Before we dive into this digital drama, let me set the stage with a little personal history. Back in the day, when dinosaurs roamed the earth and dial-up modems screeched their war cry, I cut my teeth on PHP. It was one of the first programming languages I learned, and let me tell you, it was addictive. So addictive, in fact, that I eventually contributed to the WordPress open-source project. (Don't worry, I'm clean now. I only code in Python and JavaScript these days... mostly.)
But enough about my sorted past with curly braces and a lot of dollar signs. Let's talk about the storm that's brewing in the usually calm world of content management systems (CMS), where the most exciting thing is typically a new plugin release. At the eye of this storm? Two little letters that are causing more drama than a season finale of Silicon Valley: "WP".
Tech Thoughts is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
Grab your favorite caffeinated beverage, because we're about to dive into a saga that's shaking the very foundations of the open-source world. It's a tale of David vs. Goliath, except both Davids grew up to be Goliaths, and now they're fighting over who gets to keep the slingshot.
The Players: David, Goliath, and... Another Goliath?
Let's set the stage for this drama, shall we?
In one corner, we have WordPress, the open-source darling that powers a whopping 43% of the internet. Led by Matt Mullenweg, the wunderkind who co-founded this digital behemoth at the ripe old age of 19 (way to make us all feel unaccomplished, Matt).
In the other corner, we have WP Engine, the hosting company that's been riding the WordPress wave to the tune of $400 million in annual revenue. They're backed by Silver Lake, a private equity firm with $102 billion in assets under management. Not exactly a mom-and-pop operation.
The Beef: It's All in the Name (and the Contributions)
So, what's got these two tech titans at each other's virtual throats? Well, it all starts with those two little letters: "WP".
Mullenweg claims that WP Engine is profiting off confusion with the WordPress brand. And he's not pulling any punches. In a scathing blog post, he wrote:
"WP Engine is not WordPress. It has to be said and repeated: WP Engine is not WordPress. My own mother was confused and thought WP Engine was an official thing. Their branding, marketing, advertising, and entire promise to customers is that they're giving you WordPress, but they're not. And they're profiting off of the confusion."
Ouch. That's the kind of burn that not even a good liquid-cooled gaming PC cool down.
But wait, there's more! Mullenweg goes on to accuse WP Engine of being a "cancer to WordPress" for disabling a core WordPress feature: revisions. For those not in the know, revisions are like a time machine for your content, letting you undo mistakes and track changes.
Mullenweg claims WP Engine turns this off by default to save money, not to improve performance as they claim. And he's absolutely right. It's like buying a car and finding out the airbags are optional to "improve fuel efficiency". Shame on you WP Engine!
Show Me the Money (or the Code)
Here's where it gets really spicy. Mullenweg drops some numbers that'll make your jaw drop:
"To summarize, they (WP Engine) do about half a billion in revenue on top of WordPress and contribute back 40 hours a week, Automattic (Matt's Wordpress parent company) is a similar size and contributes back 3,915 hours a week."
Let that sink in for a moment. WP Engine, with its $400 million revenue, is contributing about 1% of what Automattic does. That's like saying you're committed to fitness because you thought about going to the gym once this month.
But Matt doesn't stop there. He provides a detailed breakdown:
Automattic: 3,915 hours per week
Yoast: 320 hours per week
GoDaddy: 300 hours per week
Bluehost: 120 hours per week
WP Engine: 40 hours per week
It's worth noting that GoDaddy and Bluehost, often criticized for their WordPress hosting, are contributing significantly more than WP Engine. It's like finding out the class troublemakers are actually doing their homework while the teacher's pet is copying answers.
The Nuclear Option: Trademark Tussle
Mullenweg's not just throwing shade – he's threatening legal action. He wants WP Engine to get a trademark license or stop using the "WP" branding.
WP Engine's response? A cease and desist letter. They claim Mullenweg's comments are damaging and misleading. It's the corporate equivalent of "I know you are, but what am I?"
The Great Automattic Exodus (Or Not?)
Well, the plot just thickened faster than a MongoDB query on a cold start. Noticing that some Automattic employees would be on WP Engine's side, Matt took a bold move that would make even the most daring startup CEOs raise an eyebrow. He offered a severance package to anyone who disagreed with his WordPress direction or his WP Engine tussle tactics. The deal? A cool $30,000 or six months of salary, whichever is higher. Talk about putting your money where your mouth is!
The kicker? Only 159 employees (that's 8.4% for you math nerds) took the bait. Now, in most tech dramas, losing 8.4% of your workforce would be cause for panic, like realizing you pushed to production without testing. But in the twisted world of startup logic, this is what I call trusting your culture. It's like Mullenweg played a game of corporate chicken with his entire staff and won. The other 91.6% essentially said, "Nah, we're good" to $126M in potential severance. That's not just drinking the Kool-Aid; that's bathing in it.
Whether this move is brilliant or bonkers, one thing's for sure: whoever stayed, definitely trusts Matt’s gut.
The Ripple Effect: How Two Letters Could Topple an Ecosystem
This isn't just about WordPress and WP Engine having a spat. This showdown could set a precedent that sends shockwaves through the entire open-source world. Here's how:
The Trademark Tightrope: Although I’m on Wordpress’ side, if WordPress wins, other open-source projects might start “policing their trademarks” more aggressively. Imagine if the Linux penguin suddenly cost more than an actual penguin to use.
The Contribution Conundrum: This could lead to a new model where companies are required to contribute a certain percentage of revenue or manpower to use open-source software commercially. It's like a digital tithe system.
The Hosting Hostility: Other hosting companies might start sweating. Could we see a mass exodus from WordPress-specific hosting? We’ll see, but the ripple effects here could reshape the entire web hosting industry.
The Fork in the Road: What if this leads to a major fork of WordPress? (I’m really bullish on this thesis.) WP Engine, backed by private equity billions, could potentially create its own WordPress-like CMS. Suddenly, we're looking at a fragmented ecosystem that could confuse users and developers alike.
The Hidden Players: Private Equity's Open-Source Play
Let's pull back the curtain on something that's not getting enough attention: the role of private equity in all this. Silver Lake, the firm backing WP Engine, isn't just any old investor. They're a tech-focused PE firm with $102 billion in assets under management.
If Silver Lake's play with WP Engine pays off, despite this controversy, we could see a gold rush of private equity firms scooping up companies built on open-source technologies. The implications? A potential shift from community-driven development to profit-driven decision making across the open-source landscape.
The Butterfly Effect: WordPress and the Creator Economy
Here's another angle that's flying under the radar: the impact on the creator economy. WordPress isn't just a CMS; it's the backbone of countless blogs, portfolios, and small businesses. If this dispute leads to higher hosting costs or fragmented services, it could have a chilling effect on independent content creators.
Imagine a world where starting a blog becomes as complicated as filing your taxes. The internet thrives on the democratization of content creation. This dispute has the potential to throw a wrench in that machinery.
My Two Cents (Because You Know You Want It)
Alright, time for some patented hot takes:
The Open-Source Paradox: This dispute highlights a fundamental tension in the open-source world. How do you balance the ideals of free, community-driven software with the realities of running a business? It's like trying to be a vegan butcher – at some point, something's gotta give.
The Branding Boomerang: Imagine creating a framework so popular that everyone starts using it for everything. Cool, right? Not so fast, my young code Padawan. WordPress has basically become synonymous with "website" for a lot of folks. It's like when your mom calls every gaming console a "Nintendo". Now, Mullenweg & Co. are trying to say, "Hey, not everything with 'WP' is ours!" It's like trying to explain that not every tissue is a Kleenex. Good luck with that, folks.
The Contribution Calculation: How do you quantify the value of contributions to an open-source project? Lines of code? Hours worked? Impact of changes? We might need a new metric – I propose the "Mullenweg Unit of Contribution" or MUC for short.
The Ethical Hosting Dilemma: This dispute raises an interesting question for website owners. Should we start considering a host's contributions to open-source projects as an ethical factor in our choices?
The Unintended Consequences: Could this dispute inadvertently benefit WordPress competitors like Wix, Squarespace or Framer? As the old saying goes, when the elephants fight, it's the grass that suffers.
The Plot Thickens: What's Next in This Techo-Drama?
As this saga unfolds, keep your eyes peeled for these potential plot twists:
The Great Migration: Will we see a mass exodus of sites from WP Engine to other hosts?
The Legal Labyrinth: If this goes to court, it could set precedents that affect how open-source software is licensed and monetized for years to come.
The Community Schism: How will the WordPress community react? We could see a divide between the "WordPress purists" and the "pragmatic users" that makes the vim vs. emacs debate look like a friendly chat.
The Regulatory Reckoning: Could this dispute catch the eye of regulators? If so, we might see new rules about how open-source projects can be commercialized.
The Bottom Line
This WordPress vs. WP Engine showdown is more than just tech drama – it's a microcosm of the larger challenges facing the open-source world as it collides with big money interests. It's David vs. Goliath, except David founded a company that became another Goliath, and now they're both fighting over who gets to use the slingshot.
One thing's for sure – the outcome of this dispute will ripple through the tech world for years to come. So grab your popcorn, fire up your localhost, and stay tuned. This is one techo-drama you won't want to miss.
Until next time, keep your code open and your mind even opener.
Cheers,
- Thiago
P.S. If you start dreaming in PHP after reading this, it might be time to touch grass... or at least switch to Python for a day. Your sanity will thank you.
About the author: Former Microsoft engineer, current startup junkie. I've sold one company, building another, and spend way too much time thinking about tech.
Tech Thoughts is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
