[Kye]

WordPress supports ActivityPub now, so this is also a spat between two massive AP platforms with apocalyptic potential. Someone needs to get follower migration from WordPress to anything else on the AP fediverse done quick.

It's inter-instance conflict at incredible scale.

[CharlesW]

Whatever happens, WordPress isn't going anywhere. At worst, someone will fork and rebrand it, just like Mike and Matt forked and rebranded b2/cafelog to create WordPress. (There are already successful forks like ClassicPress.)

[sureIy]

> ClassicPress

Never heard of it before, but it constantly surprises me how much effort people are willing to put in just to keep “the old version” of something.

[bravetraveler]

I think it says a bit about how dubious 'new and improved' can be

Security updates, features? Perhaps yay. Redesign, boo. I already use the thing.

[sureIy]

Yeah, exactly. Do you really want to put that much effort because “redesign boo”? Makes no sense. Put the effort learning the new UI and move on.

Every single “bring the old X back” project ends badly, you’re just extending your own pain by using those projects because they’ll slowly fall out of date.

The only way to successfully “bring the old X back” is to convince the original vendor, like it happened for the Metro UI in Windows 8.

[chuckadams]

If it were just a matter of a new admin UI, that would be one thing. A quick peek under the covers reveals how howling-at-the-moon-insane the Gutenberg block format is, how brittle it is when working with filters and other low-level things, and that's been the real source of pushback from developers.

TBH I kind of liked Metro back when it was used for XP Media Center. Win8 just did a crap job at integrating it with the rest of the system (and arguably repeating the same crap job with win10/11)

[bravetraveler]

You've changed my mind on this a bit! I was generally more in the mindset of: "sure, maintain the old copy". Granted, Wordpress isn't the best choice for this. Vulnerabilities abound.

It's funny we still agree, coming from different approaches :) To your point, it doesn't make much sense to fork and actually maintain the code. I more meant the installation/deployment. I'm not that afraid with things like SELinux policies and network boundaries in place.

One could learn the new thing, find something more suitable, or run the old thing until the wheels fall off. We're spoiled for choice!

Creating more fragmentation/choice extends the challenge. We see this with Linux distributions. Outside of like four root distributions, we have N derivatives re-packaging for slightly different themes and configs.

Given enough time and caffeine I could replace the entire ISO ecosystem with YML and Linux from Scratch... but I use something more traditional because I value my time/effort.