Reuters blocks my VPN and the Wayback archived version doesn’t display anything.

They, notably, did not say that PHP was good.

Literally just having ollama installed and some models that work well with the amount of VRAM I have. I don’t auto-start the daemon because I rarely use it. Occasionally I use it for proof-reading/feedback on things like cover letters, or debugging. I don’t let it write anything. If it has something useful to say it can tell me in the chat and I can implement it if it’s good. Usually I don’t need it though so it just sits on my disk for the most part.

Wow, this article really reads as LLM-generated to me. The quoted section with the “We won’t pretend otherwise:”, the second paragraph in:

This post isn’t about how to update. It’s about how these vulnerabilities were found and fixed, what has changed in how PHP security is handled over the past two years, and what we need from the organizations that depend on PHP to keep PHP’s security work going.

Could they not be bothered to write a write-up about such a critical severity?

A lot of FOSS solutions have funny names, mascots, etc. I’m surprised if IT/tech workers aren’t used to it. Just politely tell them, yes, it has slightly silly branding, but look past it and it’s software that does what you want.

I mean, Wikipedia still refused to recognise the union. They have to now given the results of the vote. And I’m sure they get more than enough in donations anyway. They did before the dispute with their workers, and I doubt enough people boycotted Wikipedia over it for it to mean that Wikipedia can’t cover their costs.