Mullenweg Reignites the WordPress, WP Engine and Automattic Feud

The Start of the Conflict

This dispute began when Mullenweg accused WP Engine of benefiting from WordPress without giving enough back to its development. He suggested that WP Engine should contribute more to the open-source project and even called for users to boycott WP Engine.

The accusation didn’t go unnoticed and WP Engine fired back, saying that Automattic was unfairly targeting them and demanded that Mullenweg stop making negative statements about their company. The seas were still calm at this point.

However, things got heated up quickly when WP Engine sent a legal notice to Automattic, claiming that this was all about money—specifically, that Automattic wanted WP Engine to pay a share of its profits for using the WordPress name.

Things escalated further when WordPress.org restricted WP Engine’s access to important developer tools, making it harder for WP Engine customers to manage their websites.

Mullenweg’s Recent Comments

At a recent WordPress event, a developer asked Mullenweg if Automattic would go back to supporting WordPress development like before. Mullenweg responded that Automattic had reduced its contributions to the core WordPress software because of its ongoing legal battle with WP Engine.

According to him, Automattic used to dedicate thousands of work hours to improving WordPress, but they’ve now cut that down to just a few hours per week. He made it clear that the only way they’d restore full support was if WP Engine backed down in their legal fight.

How It Affects WordPress Developers

WordPress is one of the most popular platforms for developers. Both experienced and new developers use this platform and WP Engine is a huge part of it. This situation has left many WordPress developers feeling frustrated.

1. Less Support for WordPress Development – Since Automattic has reduced its involvement, WordPress updates and improvements might slow down. This could lead to delays in fixing bugs and releasing new features.

2. A Divided WordPress Community – Some developers support WP Engine, while others stand with Automattic. This divide is creating tension within the WordPress ecosystem, making collaboration harder.

3. Business Disruptions – Many businesses rely on WP Engine for hosting, and WordPress developers depend on a stable platform. If these disputes continue, it could impact businesses that use WordPress, forcing them to look for alternatives.

Final Thoughts

The rift between the two tech giants seems to be increasing instead of settling down. Mullenweg’s comments are not helping either. But it has badly affected the developers who rely on both these platforms.

Moreover, the fight between WP Engine and Automattic doesn’t seem to be ending anytime soon (as we can understand from Mullenweg’s latest statement). As a result, the WordPress Development Service providing community is caught in the middle.

While WP Engine claims its being unfairly targeted, Automattic insists that companies benefiting from WordPress should give back to the platform. Until both sides reach an agreement, WordPress users and developers may have to deal with the consequences—fewer updates, slower development, and a more divided community.