Comment by kmeisthax
12 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.
> 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.