I spend most of my day using WordPress. My consulting business is focused on WordPress, and clients hire me to build bespoke WordPress themes, optimise their WordPress site, or migrate a site from another platform to WordPress. That is all to say that I have skin in the game with the recent actions taken by Matt Mullenweg and Automattic.
As someone who uses WordPress all day, I know there are many things to dislike about the platform, but one of its strengths—at least to me—has been strong leadership from Matt and Automattic. Even if I don’t always agree with the future direction, I had faith that the project was in safe hands. Now, that faith is quickly evaporating. As the saying goes, trust takes years to build and seconds to break.
For those who haven’t been following, here’s an incomplete overview of the WordPress drama:
- Matt Mullenweg calls out WP Engine at WordCamp and then follows up with a blog post calling WP Engine “a cancer to WordPress”
- WP Engine responds with a cease-and-desist letter to Automattic
- Automattic then temporarily blocks WP Engine from accessing the wordpress.org plugin repo, meaning any sites hosted on WP Engine couldn’t perform plugin updates
- Automattic then takes over the Advanced Custom Fields plugin on WordPress.org, keeping their install stats and reviews
ACF is an incredibly important plugin to the WordPress ecosystem, and I use it on every site I build. It’s not a stretch to say there’s a possibility I wouldn’t be using WordPress if ACF didn’t exist. So, for Automattic to swoop in and hijack the plugin is a big deal that doesn’t sit right with me.
From what I can see, this stems from Matt believing WP Engine needs to contribute more to WordPress. He is demanding 8% of WP Engine’s revenues, so ultimately, as these things usually are, it’s about money. One could easily argue that WP Engine should contribute more to WordPress (although I have no idea how much they contribute currently). However, the way Matt and Automattic are handling this situation is hurting WordPress users and the ecosystem.
Updating plugins frequently is security 101 when it comes to WordPress, so for Automattic to block WP Engine servers from performing plugin updates is a slap in the face for WordPress users and site owners. Why should businesses and individuals who have nothing to do with this fight have to suffer?
My concern now is that while Automattic is currently attacking WP Engine, what’s to stop them from going after other hosts? One of my preferred hosts is Kinsta, who also offer specialised WordPress hosting. What’s to say Automattic won’t go after them next? And who would want to build a premium plugin when Automattic could just hijack it because they feel like it?
Right now, my business is closely tied to WordPress. However, given the severity of this situation, I’m actively exploring other alternatives. WordPress, under Matt’s control, seems like an increasing risk.
Updates
14/10/24: Tim Nash published a post about what you need to know about the Advanced Custom Fields changes
14/10/24: My friend Mike Ellis shared his thoughts on the drama: With great power comes great responsibility
14/10/24: DHH:
It’s not too late. Yes, some bridges have been burned, but look at those as sunk cost. Even in isolation, the additional expense from here on out to continue this conquest is not going to be worth it either. There’s still time to turn around. To strike a modest deal where all parties save some face. I implore you to pursue it.