That, and they flag pretty much any random patch with a CVE these days, making it harder for distro maintainers to keep up.
For this specific "bug" they took care to not mention any security angle in the commit message, making it extremely hard for an outsider to even realize this was a critical patch. I assume this was because they wanted to push the fix without breaking embargo.
I'm pretty sure Ukraine were taking the Russian preparations as what they were. And they had plans to counter them. Proven by the fact that Putin's 3 days war has now surpassed the Russian involvement in WWII.
Over here in Germany, professors' job is "research and teaching". According to the internet, the author's university is a publicly funded university as well. I can see how AI can make you faster on the research side, but you give up 100% of the teaching/developing people part.
As a tax payer, I am very concerned if the people I fund with my taxes to do a job unilaterally declare they are no longer going to do the half of it.
> Here is something that gets lost in all the excitement about AI productivity: most software engineers became engineers because they love writing code.
This resonates somewhat, but for a different reason. My mental model is that there are two kinds of developers, the craftsmen and the artists.
The artist considers the act of writing code their actual fulfillment. They thrive on beautifully written code. They are often attached to their code to a point where they will be hurt if someone criticizes (or even deletes) it.
The craftsman understands that code exists to serve a purpose and that is to make someone's life easier. This can be a totally non-technical customer/user that now can get their work done better. It could be another developer that benefits from using a library we wrote.
The artist hates LLMs as it takes away their work and replaces their works of beauty with generic, templatized code.
The craftsman acknowledges that LLMs are another tool in the toolbelt and using them will make them create more benefits for their customers.
Profiting from selling their patchset is not the whole story, though. grsec was public and free for a long time and there were many effects at play preventing the kernel from adopting it.
Professionally he's running a successful code/security consultancy [2]. This pays his bills, so that nerd-wise he is running his own web server and content management system where everything is self-written, inclusive of his own libC implementation with a focus on bare minimum requirements. [1] He's been around in the German IT community for decades and was earlier involved in Chaos Computer Club (CCC) where he still used to attend their annual congress, which is kind of the "meet and greet" of the German IT community.
His self-hosted blog was/is very popular/controversial. He is pretty opinionated on nearly everything and he's not taking hostages when he criticizes someone. So the "woke" people don't like him, the nazis don't like him, the corpo guys don't like him. And he pretty much doesn't care.
Earlier this year he apparently suffered some critical health condition and went quiet without notice for more than 6 months, I believe.