aldavigdis
Joined 2 years ago
Joined 2 years ago
Do you think I'm fucking stupid?
I actually doubt there's much left of Matt's own code besides some of the crap that should be removed, such as hello.php.
(Anyway. Matt. If you're reading this, then I've seen you've been very generous with your checkbook for the past couple of weeks. I am open to burying the axe to a certain extent but that would require paying for estimated unpaid overtime and on-call hours, providing proper compensation for keeping me for almost a year on a trialmattician contract and destroying my mental and financial well-being among other things. You know how to find me. If not, I'll see you in Brussels.)
I do worry about the thousands of people out there that have no other marketable skill than WordPress and are not going to climb out.
The issue is how WordPress seems to be stuck in the ways of the mid-2000's. You can be a "senior full stack" developer in the WordPress ecosystem but you'll hit a wall once you start applying for more general PHP roles as everything from the standard coding style to how classes and namespaces are used are worlds apart.
I am worried that he feels like he's losing the grip he has on his holy trinity of corporate entities and that he'd rather burn it down as he steps down than letting an actual open-membership non-profit or a consortium take it away from him.
In fact, I've seen a handful of sites that have a "blog" on them, but they don't use the Posts feature for it.
WordPress is a massive monolith despite its extendibility and the thing is that Matt get veto anything (this is why his hello.php plugin is still included as a form of digital manspreading) and many of the unpopular decisions are based on the needs specific to Automattic, like how the wp_posts table was used for pretty much everything until relatively recently.
The foundation was open about the use of the WordPress logo, wordmark and the WP acronym until a couple of weeks ago. (Here's the previous version of the trademark policy (https://web.archive.org/web/20240101165105/https://wordpress...) and here is the current one for comparison (https://wordpressfoundation.org/trademark-policy/))
Just like with attaching a permissive license to your code means that you can't just yank it back when you feel like it, there's a long history of case law proofing that you can't do the same with trademarks, especially when there's a whole economy that has built up around your FOSS project.