He's a writer/journalist (yes).

It's always the engineer's fault when you are making reverse centaurs.

I put together a prototype that allows you to use containerized Debian packages a few years back: debexec However, folks didn't seem interested in it. I personally think that moving further away from package management is a mistake and that we should be making packages better instead.

The omnibus gitlab install isn't hard to administer, it only gets tricky if you're trying to run different pieces of the system on different servers.

LLMs: The JPEG of Knowledge is worth a read.

They're not dumb, they're _intentionally_ socializing the cost of using OSS so that they don't have to fix the problems they "find" that affect them.

When War for the Over world first came out I sent them stack traces for some crashes and they really seemed to appreciate that. I can't remember if it was them or someone else, but somebody said something like "Linux users may be 1% of your users, but they provide 99% of your actionable bug reports".

It's called a "win-win" scenario, either you make your work go faster or they can fire you. Either way they win.

They broke the unattended upgrade facility and didn't seem to care, so "yes".

If you are running 32-bit wine then you can run 16-bit programs, though they are working on bringing 16-bit support to 64-bit wine.

Be careful what you wish for, an executive order against "subversive research" would not be totally unexpected given how things are going right now. But I don't know that it would throw the people you want in jail...

Well, when you have all your code generated by an AI code generator, reviewed by an AI code analyzer, and approved by an AI manager then what exactly do you expect?

The requirements are the things that people can think of ahead of time, and they always contain glaring problems. It is inevitable that someone will have a "shower epiphany" at some point and share it with their colleagues. When these discussions happen in person then there's a discussion about how important it is, whether it rises to the level of an ECR, NCR, or other documentation mechanism, and what to do about it next. I have seen myself that when this happens in Teams chats that _usually_ someone from PMO intervenes immediately and says that we don't have the budget to address the issue and don't you dare spend any more time on it.

Yeah, I think it would be far more likely that they would offer publishers a slightly reduced fee. "Instead of charging you 30%, we'll charge 25% if you make it work on Linux".

And for the ones who have families, moving the family is the wife's job ... and she can move or quit ;)