←back to thread

Our New AI Website Builder

(wordpress.com)
93 points bookofjoe | 4 comments | 11 Apr 25 14:36 UTC | HN request time: 0.427s | source
Show context
nadermx ◴[11 Apr 25 17:12 UTC] No.43656145[source]▶
Speaking of WordPress, hows the entire WordPress debacle going with Matt Mullenweg?
replies(5): >>43656439 #>>43656600 #>>43656607 #>>43657123 #>>43657533 #
1. cabalos ◴[11 Apr 25 18:00 UTC] No.43656600[source]▶
Development has dropped off a cliff over the last couple of months. The release cycle has moved from quarterly to yearly. He's basically taking his ball and going home. My guess is we'll see more internal initiatives like this AI builder instead of focusing on the core product.

This would be an okay strategy if his core product wasn't in such a state of disrepair. I've seen multiple issues on Github projects from Automattic developers saying "this would be easy to fix upstream but we're not allow to fix anything in WordPress right now." It's pathetic and actively harming his own business.

replies(2): >>43657007 #>>43658438 #
2. cdolan ◴[11 Apr 25 19:25 UTC] No.43657519[source]▶
"it's pathetic that no other company benefiting from WordPress has stepped up either"

^<-- hard to justify doing so when Wordpress' package ecosystem (the open source platform) is tethered to Wordpress.org (matt's personal website)

replies(1): >>43660024 #
3. molochai ◴[11 Apr 25 20:54 UTC] No.43658438[source]▶
Disrepair is too right. 5k issues and 1.7k open PRs on the Gutenberg GitHub repository.

I wish this all had happened before Full Site Editing was put into .org.

4. cabalos ◴[11 Apr 25 23:58 UTC] No.43660024{3}[source]▶
Also, good luck sending in a PR and getting it merged. Unless you are part of Matt’s inner circle, it isn’t happening. Even the most basic bug fix PRs are routinely ignored.