+1 for this. This is kinda the same issue with encoding, just UTF-8 everything and move on.

Capable developers touch whatever language is required to get a job done.

There isn’t much of a difference between writing a theme for Guthemberg and the classic editor. In fact your current theme should work just fine in Guthemberg as it just adds the extra html for the built in blocks to your posts / pages. You aren’t required to create a block based theme and split everything into blocks, that’s kind of a myth around Guthemberg.

That or you develop your theme with the features you need baked in. This is the irony of the Hugo people, they’re capable developers that can make themes but they can’t just create a simples Wordpress theme from the ground?

Yeah, everyone with a decent amount of content will just pick Wordpress and move on. It works, it’s reliable, it’s well supported and will keep running for decades at least.

The article misses one thing, typically companies that use XGH can’t keep most developers around for more than two years. You end up with teams that are constantly changing members and there are usually 2 or 3 very old guys that stick around and doesn’t give a shit either way.

When you get to a job and you find that all people are new and there are new teams being created for everything and whatnot that’s a very strong signal that XGH is employed on that bussiness.

PHP -> Problem -> Replace the developer -> Solution.

Yes PHP was bad in 5.x, in 8.x if things go bad it’s just the developer who’s bad.

Only if people actually tried to learn PHP.

I don’t see a problem with this, seems perfectly reasonable an API that let’s you query whatever you want. By drawing attention to this you might get some “easily offendable people” to notice OSM and make a fuzz about this which will result in a worse API for everybody.