Last year was absolutely wild. For those who didn't follow all the threads, tweets, and secret Slack channels in real time, this blog offers an excellent recap—complete with popcorn-worthy drama.
Then suddenly... silence. No new statements, no live rants—just radio silence. Probably because Matt Mullenweg's company Automattic and their biggest competitor WP Engine are currently dragging each other to court, and everyone involved would rather keep quiet until the trial date.
But while the popcorn was being put away outside, things were just heating up behind the scenes. The wave spilled over from the WordPress corner into the entire open-source ecosystem—and suddenly, the sales drones of closed-source vendors had a new favorite talking point:
"Sure, back in the day, the argument 'Open source is insecure because the code is visible' was popular, but hardly anyone buys that anymore. So now we're pushing the narrative 'Open source is dangerous because some unhinged dictator could ruin your entire business tomorrow.' Just look at what's happening with WordPress right now!"
Whether they couldn't be bothered to check if the WordPress scenario actually applies to every other FLOSS community or if it just conveniently fit their agenda to generalize, who knows. As long as the glossy slides were printed and the WP drama stood as a big boogeyman on slide 7.
And the WordPress community itself? Remarkably quiet. The big players don’t want to bite the hand that feeds them—understandable, but also a little disappointing.
So the pushback had to come from outside—from friends in the FLOSS ecosystem.
Maintainer? None other than the Linux Foundation. Someone actually built a new project out of the shitstorm—respect!
Supported by