The blocked resources in question? Automatic security and features updates and plugin/theme repository access. Matt Mullenweg reasserted his claim that this was a trademark issue. In tandem, WordPress.org updated its Trademark Policy page to forbid WP Engine specifically (way after the Cease & Desist): from “you are free to use [‘WP’] n any way you see fit” to a diatribe:
The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.
https://techcrunch.com/2024/09/26/wordpress-vs-wp-engine-drama-explained attempts to provide a full chronology so far.
That would be great but the reality is that client’s mindsets need to change. I tried to explain to a client that Wordpress is not a good fit for their complex web application and yet they didn’t wanna switch to anything else. People are way too worried about new tech and wanna stick with whatever they know, even if it causes massive problems.
Wordpress is not a good fit for virtually any modern application. It’s designed as a blogging platform and basically no one makes blogs anymore. That functionality kind of got eaten up by Facebook and Twitter and LinkedIn, so no one needs blogs.
Instead of letting WordPress die the death it most definitely deserves they shoehorned in functionality, which would be fine if it wasn’t such a bodge job.
Seriously. People want to shove everything into Wordpress then get cranky when you can’t make Wordpress into a ecommerce store, marketing platform, personal blog, file sharing service, and NFT marketplace.
And then it gets hacked because they needed 14 SEO plugins, 2 different form plugins, and were not going to pay for managed updates because that’s easy they can do it themselves.
If you’re trying to turn WordPress into an application, for christs sake go use Django, Laravel, or Rails. Don’t send a CMS to do an applications’ job.
Shit you don’t even need a CMS at this point. I moved off WordPress to Hugo and SFTP and i’m happier than a pig in shit. Shit loads fast and no external threats.
Wordpress is the Excel of CMSs. It can do just about anything, but at this point it barely manages content well.
That’s a great analogy actually. You can do almost anything with it but what the vast majority of people choose to do with it is wrong.
Just like how people insist on using Excel as a database or Excel as a form.
I haven’t done web work for well over a decade and recently was surprised to learn that Wordpress is still very relevant. I remember back then, seeking alternatives as we expected it to become more of a legacy thing a few years down the track, so we were on the lookout for future-proofing client sites with a better foundation. At that point it was a decade old and annoying af because it morphed into a messy way of doing websites because people misused it’s original purpose. Brain had to think like a blog and then trick it into doing what you want, kind of like using tables to structure pages before CSS-P saved the day.