When this story first emerged, I was somewhat sympathetic to Matt/Automattic. But geeze, he is just looking worse and worse. Between this tantrum and threatening a former employee over a very innocuous statement [1], his credibility is pretty low in my opinion.<p>[1] <a href="https://medium.com/@kelliepeterson/nice-guy-matt-mullenweg-ceo-of-wordpress-com-cries-foul-and-threatens-me-with-legal-action-f116ac57d862" rel="nofollow">https://medium.com/@kelliepeterson/nice-guy-matt-mullenweg-c...</a>
> <i>"Neal has been adverse to Quinn Emanuel a number of times, and won every case."</i><p>I don't think I have ever before seen, in an official public statement, a "The lawyer we just hired always beats the lawyer they just hired!" boast, and it seems ridiculous - it's almost even hinting in the direction that they think the case should be decided on quality of lawyer rather than that their case should win on merit.
<i>From our earliest days, our highest priority has always been our customers. WP Engine can hardly say the same.</i><p>Yes, that's why WordPress silently and secretly licensed back the WordPress trademarks to Matt's for-profit company without telling anybody. For the good of the customers.<p>That's why they forced the new boondoggle editing UI that everyone hates. For the good of the customers.<p>That's why the WordPress code <i>is still</i> spaghetti more than 15 years after it was originally launched. For the good of the customers.<p>Matt also seems very proud of his new, shady lawyer, who failed to disclose that he had cases before the Supreme Court when he endorsed Gorsuch and Kavanaugh for open spots. Gorsuch and Kavanaugh have since reciprocated by ruling for this guy's clients every time, in several cases with decisions that confounded even conservative legal experts. So, it would seem Matt found a dirty lawyer to represent his dirty case. (EDIT: Katyal is the lawyer who suggested corporations should be immune from anti-trafficking laws <i>because it would be bad for business</i> and got his endorsee pals to bless corporate wage theft. He's the kind of lawyer companies turn to when they want to get away with something truly evil.)<p><i>We vehemently deny WP Engine’s allegations—which are gross mischaracterizations of reality</i><p>Based on Matt's gross misrepresentations of reality on yesterday's thread, the only party to this case making gross mischaracterizations of reality is Matt.<p>If WordPress were truly an independent, community-led organization like Matt claims, he would have been forced out by now for the harm he's inflicted upon it.
The legal victory is almost moot, even if Automattic is found to have acted in their rights. How does any Wordpress developer know they are not going to be next? Or all of the third party plugin providers? Or theme makers? All of them heavily use Wordpress branding in their services, few contribute to the open source.<p>The precedent being set here is <i>wild</i>, and every Wordpress organization becoming a Mullenweg personal mouthpiece account defending him personally is just so, so, bad.<p>This is one of the the most needless self-destructive acts I have ever seen in the world of business.
WP Engine should consider challenging the Wordpress Foundation's 501(c)(3) status by filing a complaint with the IRS. IANAL but I have run nonprofits, and they must be very careful about how it interacts with a for profit entity, especially when they share staff.<p><a href="https://www.irs.gov/pub/irs-tege/How%20to%20Lose%20Your%20Tax%20Exempt%20Status.pdf" rel="nofollow">https://www.irs.gov/pub/irs-tege/How%20to%20Lose%20Your%20Ta...</a>
> "WP Engine can hardly say the same"<p>So much of Automattic's corpospeak drips with spite. Makes me understand why other companies are so "bland" — to protect themselves
This is getting embarrassing. I was a big fan of Matt's before this whole charade started but he's basically flushing 20 years of goodwill down the drain for not a whole lot in return. As best as I can tell this is all over a trademark dispute over the "WP" in WPEngine (and a hand-forcing by Automattic to implement a retroactive licensing agreement)?
# A Statement from Automattic<p>Last night, WP Engine filed a baseless lawsuit against Automattic and Matt Mullenweg. Their complaint is flawed, start to finish. We vehemently deny WP Engine’s allegations—which are gross mischaracterizations of reality—and reserve all of our rights. Automattic is confident in our legal position, and will vigorously litigate against this absurd filing, as well as pursue all remedies against WP Engine. Automattic has retained Neal Katyal, former Acting Solicitor General of the United States, and his firm Hogan Lovells, LLP, to represent us. Mr. Katyal stated, “I stayed up last night reading WP Engine’s Complaint, trying to find any merit anywhere to it. The whole thing is meritless, and we look forward to the federal court’s consideration of their lawsuit.”<p>Our focus is and has always been protecting the integrity of WordPress and our mission to democratize publishing. From our earliest days, our highest priority has always been our customers. WP Engine can hardly say the same.
Regardless of which side you're on, so far the one thing that seems clear here is that the lawyers are going to be the real winners here.<p>When that is happening between two companies I generally don't care about it that much, but I hope open source doesn't turn out to be collateral damage here.
Like many here I suspect I care less about who wins the litigation than about the third parties - businesses, individuals and at least one major charity - who will have been affected by Matt’s and Automattic’s actions.<p>Where is the blog post about the affect this has had on them?
This feels like a classic "you either die a hero or live long enough to see yourself become the villain". It appears the more Matt talks, the more he tarnishes the reputation Wordpress has.
Nobody seems to have noticed that Matt Mullenweg stopped responding to everyone everywhere (including HN) after they hired the external law firm. They likely told him to shut up.
I get it that there are probably a lot of people here to depend on Wordpress for their work or personal blog or whatever but ... do we really need daily updates and discussion on this spat between two companies?<p>I've probably answered my own question already because evidently a lot of people here find this kind of schoolyard scrap intriguing ... I just wonder ... why. I guess the answer is to just upvote everything else on the front page.
The popcorn value on this saga is awesome!<p>As far as I can figure, from watching Matt's recent interviews and my own conjecture...<p>Matt's seen his open source creation go, over the course of 20 years, from a hobbyist product to now one with a multitude of companies creating billions of revenue from it.<p>But as it's grown certain companies are now huge and flush with VC cash. Which does change the equation. In the early days it might be reasonable to turn a blind eye to trademark infringement when it helps all boats rise, but now things are very imbalanced.<p>IMHO WPEngine is rent-extracting in the same way that AWS does with many open-source solutions. Customers want products not source-code and are prepared to pay for packaged value-added products compatible with Wordpress.
But none of this revenue is going back to the developers and fostering the development ecosystem in any meaningful way.
If opensource projects like Redis & Elasticsearch could have had developers hired from 8% of revenues from those AWS sales imagine how much better off those projects could have been.<p>As Wordpress itself is open-source Matt doesn't have any levers except the name Wordpress. As anybody in open-source should know - the code might well be open for forking but the name is very protected. Just because the trademark hasn't been entirely well enforced doesn't mean the protection is lost - the right always belongs to the trademark holder to use and enforce how they please as unilaterally as they wish. Trademarks can lose their protection if they start referring to generics but that's not the case here. Wordpress doesn't mean generic CMS - it's always referring to a Wordpress source code hosted by various companies.<p>Matt's clearly acting emotionally and not terribly logically - that's clear for everyone to see. But I do think its with the long term intention of making a more sustainable community.<p>Ultimately WPEngine can just rename their company and the only lever Matt has over them goes away.<p>Or they can embrace the name and pay a fair licensing cost - a rate significantly lower than if they were licensing some other commercial CRM software.
Medium term WordPress itself and the participants in its ecosystem are going to be the losers here.<p>As a normal WordPress user who is a current client of Automattic AND WP Engine (for different sites), I’m simply far less likely to use WordPress at all for anything new. Why would I at this point? Why would anyone?
Who is actively using Wordpress in 2024? It’s been a shithole product for shitty websites since it’s been a thing………<p>Shitty performance, shitty themes, borderline malware plugins……