"Automattic vs WP Engine: The WordPress Drama is Driving Me Crazy"

“Automattic vs WP Engine: The WordPress Drama is Driving Me Crazy”

Automattic and WP Engine: Like Two Mates Arguing Over Who’s Got the Finest Greggs Pasty

Opinion – Alright, I’ve had it with this ridiculousness now. I’ve been working with WordPress since all the way back in 2003. At that time, we were ditching clunky nonsense like Vignette – which, by the way, got swallowed up by OpenText if you’re interested. WordPress back then was a fresh breeze. Super easy to use, open source, and – the greatest part – free! It was the ultimate solution for web publishing, I tell you.

But fast forward to today, and we have Automattic (the team behind WordPress.com) and WP Engine squabbling foolishly. Honestly, it’s like watching two blokes in the Bigg Market at 1 a.m., both convinced their takeaway pizza’s superior to the other’s. Only this time, instead of pizzas, we’re discussing forks of open-source code, WordPress itself, and a hefty dose of corporate posturing. Sounds amusing? Aye, it’s not.

The Fork Heard Round the Internet

So, here’s what’s happening. WP Engine – one of the major WordPress hosting companies – decided to fork (that’s a posh term for “copy and modify”) WordPress, and they’re calling it “Atlas”. Why? Apparently, WordPress isn’t “modern” enough for WP Engine’s vision. Fair enough, if you believe that excuse. Personally, I reckon someone’s had too many craft ales and thought they needed to go off-script.

Now, Automattic, who essentially manage WordPress.org, are not pleased. Understandably so, I might add. Automattic’s CEO, Matt Mullenweg, has already weighed in, calling WP Engine’s decision a poor move on their part. He’s out here throwing verbal jabs like he’s Mike Tyson in the tech arena with: “Atlas isn’t WordPress,” and “They’re undermining the platform.” Ooft. Quite spicy, isn’t it?

Automattic vs WP Engine: The WordPress Drama is Driving Me Crazy

Open Source or Open Disputes?

WordPress was founded on the principle of open-source cooperation, right? It’s akin to a massive Geordie family chipping in to create something better. But this? This is like your uncle swiping half the bricks to construct his own shed and then claiming it’s superior because he slapped a bright orange coat on it.

Don’t misunderstand me, forks in open source aren’t innately bad. Sometimes they spark innovation, no doubt? Linux boasts about 50 billion versions, and some of them are top-notch. But this? It feels more like a pissing contest than genuine progress. It sets a poor precedent for what’s meant to be a community-centered initiative. Publicly clapping back just harms the ecosystem.

Why Should You Care? (Spoiler: You Might Not, But You Should)

If you’re a WordPress enthusiast – like this daft character here – you ought to be somewhat worried about the ripple effects. WP Engine’s customers might get drawn into their Atlas ecosystem, potentially creating incompatibility problems in the future. And for those of us using standard WordPress? We could find ourselves caught in a tech tug o’ war. The whole point of WordPress is its adaptability and wide compatibility. Mess that up, and you’re just creating more headaches for everyone.

Automattic vs WP Engine: The WordPress Drama is Driving Me Crazy

A Case of Inflated Ego?

Here’s the cold hard truth, since you lot are aware I don’t mince words: WP Engine are getting a bit above themselves, while Automattic’s reaction feels as petty as a teenager discovering their mate is copying their hairstyle. Both parties could benefit from sitting down, calming down, and refocusing on what matters – improving WordPress for all us grumpy souls who rely on it.

Otherwise, this “fork” will just end up jabbing everyone in the backside. Charming image, that, isn’t it?

Final Thoughts: Can We All Just Get Along?

Look, the open-source realm flourishes on collaboration, not squabbling. Automattic and WP Engine need to convene, resolve this nonsense, and concentrate on what really counts: keeping WordPress exceptional. It’s not about who has the biggest coding ego; it’s about easing things for us lot who have to utilize the darn thing. Simple as that.

Forks at dawn… but it’s not a good look for open source

Summary: Automattic and WP Engine are at it like kids on a playground over the future of WordPress. It’s amusing for the moment but somewhat concerning for the rest of us. No one comes out on top when the big players tussle – except maybe lawyers. Sort it out, lads. You’re stressing me and my Jack Russell out.