Comment by kmeisthax
15 hours ago
I am saying this as someone who has had repeated and ongoing issues with WP Engine as a hosting platform: no, Matt Mullenweg was not even valid in his basic assumptions motivating his lawsuit against WP Engine. The idea that a hosting platform is leeching off the WordPress ecosystem is absurd, for two reasons:
1. WordPress is free and open source software, developed under reciprocal licensing (GPL). Hosting companies are neither legally nor morally obligated to contribute back to WordPress core. They are already a beneficial part of the ecosystem.
2. WP Engine was contributing back to the WordPress ecosystem, just not Matt Mullenweg's corner of it.
WordPress is a modular platform and plugin and theme developers are just as important to WordPress's continued success as core development is. WP Engine happens to own Advanced Custom Fields (ACF), which is basically WordPress's answer to the Drupal Fields API[0]. ACF is what lets you add arbitrary fields to WordPress's page edit screen without having to write a bunch of custom metabox hooks and forms. It was a huge timesaver before things moved to page builders[1] and it's still useful even if you're using a page builder.
[0] Formerly Content Construction Kit
[1] Full disclosure: I hate Gutenberg. It is not WordPress, it's a React development kit tumor shoved inside WordPress. Any other page builder would be preferable.
> WP Engine happens to own Advanced Custom Fields (ACF), which is basically WordPress's answer to the Drupal Fields API.
The speed with which Matt hijacked that plugin was one of the funniest parts of this saga. All while complaining they don’t contribute!
Finally a sane comment. If you actually watched the interview with Theo, he openly admits to just randomly throwing in a demand of arbitrary percentage of their sales. The whole episode is actually insane.
I'm still wondering who's the target audience for something like Gutenberg.
- A bastardized version of React whose state is stored in...HTML comments and WordPress shortcodes. It's extremely brittle and even simply updating an article can put its content into an unrecoverable state.
- Some components are done in javascript client side, some are done PHP server side, there's virtually no clear idea when to use which.
- It's incredibly developer hostile compared to basically any existing WordPress Visual Builder. We're at version 23.9 and it still breaks its API and behavior to the point of forcing full component rewrites (see the changes between Blocks v2 and v3 in WordPress 7.0)
- Its full editor capabilities are basic at best. The default components are incredibly shallow, and to get even a somewhat decent layout you're at the mercy of third-party developers, by that point you could've avoided many issues going straight to Elementor or WP Bakery.
- It's incredibly confusing for the end-users! The default behavior of the editing tools is to appear only when a block is selected, which is kinda difficult when the blocks themselves are invisible. Also, the "everything is a component" approach means that every paragraph, every list, every heading is a standalone gutenberg component with his own properties that could affect every other block on the page. Writing something requires constantly going back and forth from the "Component Tree" view just to make sure there's no empty components floating somewhere disrupting the page when viewed on a tablet.
It's...truly the worst of every possible worlds, and much of its issues are blatantly self-inflicted. I genuinely can't think of any reason to use it compared to any other alternative.
WP Engine didn't make ACF, they acquired the company that acquired the OG creator of the plugin.
Their contribution to the plugin was a switch to a subscription-based model and they also started reaching out privately to theme authors with ambiguously-worded emails that could be interpreted as them forcing you to stop bundling the plugin with your theme (we had a lifetime license) and directing customers to their sales. Personally I chose not to engage with that communication.
The fight between Matt and WP Engine was messy and I agree with most of your points but I also do think that forking ACF into SCF was a net positive for the community.
He didn't say they made it, he said they _own_ it.
The issue was not that forking of ACF in and of itself was controversial. It was that they hijacked and repurposed the original WordPress Community page and distribution to point to their own, including any subscribers to the existing project in the name of "security".
One could argue that because WP Engine was banned from accessing the WordPress.org infrastructure, it could technically be seen as a form of supply chain attack and brought up questions about trust and possibly monopolistic and anti-competitive behavior.
> but I also do think that forking ACF into SCF was a net positive for the community.
I think you can make the case that in principle this fork was a good idea. (Though I personally feel ACF is architecturally bad)
What I think is unarguable is that the way that fork happened, including the commandeering of the slug to pervert the auto-update mechanism, was both improper and self-destructive, and was pretty indicative of the impairment of Matt’s decisionmaking and seriousness.
I agree, introducing it into the core should have and could have been a constructive move way before given how important the plugin is in the WP ecosystem.
When and how it happened was a hilarious plot twist nobody expected.
> WordPress is free and open source software, developed under reciprocal licensing (GPL). Hosting companies are neither legally nor morally obligated to contribute back to WordPress core.
Many an old open-source project ran into this trap. Elasticsearch is one good example. Back when the old GPL era open-source projects were invented, the idea of third parties taking open-source software and just making a shitload of money with it was unthought of - and certainly not at the scale of Amazon AWS.
The only counterexample was Wikipedia's MediaWiki, it similarly is GPL but from the start it was clear that there would be at least one commercial side actor - Wikia, nowadays called Fandom.