Earlier quoted context omitted.
Yeah, exactly! No reason for it to collapse into ashes like the Wordpress “I dream of ruling an ecosystem by refusing to charge money” plans will, even if certainly as an old thing it’s old.
You might want to visit https://www.typepad.com/pricing as a logged-out user, and read the entire pop-up (which has been present for 4 years now) before saying that...
Matt Mullenweg temporarily shuts down some Wordpress.org functions
121–130 of 130 posts
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#122Earlier quoted context omitted.
My working theory is that investors are pulling up ladders now that interest rates are VC-unprofitable, and so either he finds a way to increase growth in profit y-o-y or they bail and let him crash like TypePad did years ago. (Except TypePad had paying customers, so their bandwidth bills weren’t anywhere near the looming threat WP is presumably facing.)
What he’s doing is basically what every cloud provider does but for some reason he is demonized even more
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#123I wish for his sake he had a good friend to take that shovel away from his hands and take him on a long, contemplative, peaceful hike. Money truly can't buy everything.
It mostly can, but you need to be willing to actually buy it ( 人 •͈ ᴗ •͈ )
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#124Earlier quoted context omitted.
You might want to visit https://www.typepad.com/pricing as a logged-out user, and read the entire pop-up (which has been present for 4 years now) before saying that...
I'm aware, but to explain the parent comment for the other readers of the site: Typepad wasn't able to continue operating through one of the dotcom crashes as an independent concern, but their hosting servers and customers were sold intact to another business, which continues to operate the TypePad servers for existing paying customers only.
No new users means Typepad's revenue will only ever shrink, which bodes poorly for the service's future. Having a massive intricate Perl codebase doesn't help either – it was designed to scale relative to aughts-era hardware, for a much larger audience than it currently has. Its future was already bleak in 2010 when Six Apart (its original owner) was acquired by VideoEgg, which came about largely because WordPress/Automattic absolutely won out over Movable Type and Typepad for blogging software market share.
As a former Six Apart employee, I'm glad that Typepad is still around 14 years after all that, but I'd be surprised if it continues to exist for much longer.
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#125This is just a play to pretend that WordPress.org is run by volunteers when in truth it's entirely run by Automattic. If it was actually ran by volunteers, he couldn't make any of it stop... because people volunteer their time without being told what to do. I can't wait for him to lose millions of dollars for a hissy fit. It's going to be delicious.
Let’s not take pleasure in someone destroying their life because they don’t have the support they need.
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#126Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#127[flagged]
I know it isn't necessarily hacker news standard, but I greatly appreciate when submitters summarize the actual content rather than post vague titles like "What's Next" or "The Real Story" or whatever.
Either get rid of the guideline or enforce it all the time.
The removal of "why" and "how" from the start of titles automatically is also fucking stupid.
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#128[flagged]
It's not really editorializing, since that means adding opinions. The HN title is currently a factual summary of the situation, without any particular flavoring. It's not "Matt throws a tantrum, takes toys and goes home" or anything like that. In cases like this where the original post title is pretty useless, I'm in favor of expanding it a bit.
It's HN's stupidest guideline.
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#129I run a WordPress agency and I'm absolutely horrified by all of this. It's not cutting through to our clients yet, but building on WordPress suddenly feels incredibly risky when one person can throw their toys out of the pram - the pineapple checkbox is just fucking ridiculous - and derail an entire ecosystem. I really wish there was some kind of mechanism to cut Matt entirely out of WordPress because he deserves to…
I’ve been chatting to my partners about this, and we aren’t planning to deploy anything net new on WordPress indefinitely.
In one respect it’s a shame to give Matt that power. On the other hand, I can’t control that he’s showing his ass, and I’m not risking my business or client deliverables on an unstable ecosystem.
Re: Matt Mullenweg temporarily shuts down some Wordpress.org functions
#130Earlier quoted context omitted.
> Except the injunction was against .com, not the .org Against .com (Automattic) and .org (Mullenweg as an individual) > Part of the case is that he is muddying the water on purpose and the separation in two entities Three, actually: WordPress Foundation, Automattic Inc., and Matt Mullenweg (as an individual)
Ah yes, you're right, I meant "was against the .com not the foundation" but even I got confused ...