3 ms·
The issue at hand seems to be WP Engine using Automattic-sponsored infrastructure for their own for-profit services, not modifications to free software.
by gtirloni 2y ago
The issue at hand seems to be WP Engine using Automattic-sponsored infrastructure for their own for-profit services, not modifications to free software.
- lolinder 2y agoThat's the place that Matt decided to hit them, but that's not where the complaint lies. The complaint as laid out in the blog posts [0][1] is nearly identical to the complaints that Elastic had against AWS: trademark use causing confusion and drawing customers away from the "official" offerings. Beyond that, Matt absolutely has beef with modifications that WP Engine has made to the free software, going so far as to say that these modifications mean that what they're offering is "not WordPress". Never mind that WordPress.com is likewise a bastardized modification—that's okay because it's "us" doing the modifying! > This is one of the many reasons they are a cancer to WordPress, and it’s important to remember that unchecked, cancer will spread. WP Engine is setting a poor standard that others may look at and think is ok to replicate. We must set a higher standard to ensure WordPress is here for the next 100 years. This kind of attitude is incompatible with the premise of Free Software, which places a strong emphasis on encouraging reuse and modification to suit user needs. [0] https://wordpress.org/news/2024/09/wp-engine/ https://wordpress.org/news/2024/09/wp-engine/ [1] https://wordpress.org/news/2024/09/wp-engine-banned/ https://wordpress.org/news/2024/09/wp-engine-banned/
- gtirloni 2y agoI haven't been following the drama since the beginning so thanks for the perspective. Totally agree this isn't good.