Matt is not WordPress | WordPress Drama Explained – WordPress vs WP Engine Conflict Timeline and Its Impact on the Whole WordPress Ecosystem
Before I say anything, I want to express my deep appreiciation for Matt Mullenweg for creating WordPress and for bringing it to the position it holds today. His dedication over the past 20 years has significantly contributed to the growth and success of WordPress, which has become one of the most widely used content management systems globally. As of now, WordPress powers over 40% of all websites on the internet, an undeniable proof of its impact and reach. I am incredibly grateful for his work. Without WordPress, I would not have earned the title of “Techie” among my peers, even as a non-coder. I created my first website in 2007 using WordPress, and I’ve continued to rely on it ever since.
However, it really hurts to see what’s happening in the WordPress world right now, and it hurts even more to witness Matt behaving in a way I had never imagined. It seems like Matt is not ‘The Matt’ anymore, the visionary leader who once inspired countless developers and enthusiasts to embrace open-source principles.
It all started in mid-September during WordCamp US, a key event in the WordPress community where developers, contributors, and enthusiasts gather to share knowledge and ideas around WordPress. During this event, Matt publicly called out WP Engine for not contributing enough to the WordPress community while profiting significantly from the free resources available on WordPress.org. He labeled WP Engine a “cancer to WordPress” and emphasized that “WP Engine is not WordPress” in an official blog post. This statement sent shockwaves through the community, sparking heated debates about the responsibilities of businesses that benefit from open-source projects.
