I've used WordPress for 20 years, and I've stopped recommending it
zenincognito
16 points
14 comments
October 27, 2026
Related Discussions
Found 5 related stories in 119.7ms across 10,780 title embeddings via pgvector HNSW
- I Stopped “Creating Content” mtlynch · 160 pts · July 20, 2026 · 47% similar
- Why developers are ditching GitHub for Codeberg and self-hosting alternatives Gedxx · 349 pts · July 09, 2026 · 46% similar
- Why don't more developers "use the platform"? vinhnx · 49 pts · October 04, 2026 · 45% similar
- Twenty Years of jQuery: How a Little Library Rewired Web Development theanonymousone · 27 pts · September 05, 2026 · 45% similar
- Matt Mullenweg Orders Accessibility Revert, Bans Core Wordpress Committer slyall · 13 pts · October 16, 2026 · 45% similar
Discussion Highlights (6 comments)
StephenTynan789
seems like these days ai can create a better design layout and backend than WordPress in significantly less time. It's lost its edge in spinning up semi-complicated websites quickly. Any site I can create on wordpress I could have Ai replicate or recreate in a matter of hours.
gnabgib
Yesterday it was a Show HN[0] about how you've built a CMS.. today it's a blog post about the incumbent. Of course you don't recommend your competitor, you probably never did. [0] https://news.ycombinator.com/item?id=50256725
bemtevi
The number one criticism against Wordpress seems to be the plugin architecture. But if you only use a small set of plugins, maybe Akismet, and Loginizer, you can do a lot of things already. Plenty of people don't need many plugins. So maybe this alternative CMS is good too, but I think for a basic blog/website Wordpress is still a good choice. Of course, the author has a point if you have to use hundreds of plugins....
dofm
“Can’t bill a minute of it” is the crux of the problem. There are all sorts of ways you can improve the management of customer WP sites. You can put each site in its own small VM, with caching, with FrankenPHP, set that up with cloud-init, manage the entire fleet remotely with WP-CLI, etc. You can have your own themes, lock down your plugin choices, only use your own code in functionality plugins, all that. But if your customers can administer the sites, something is going to burn you nonetheless, and when it happens nobody is paying. Part of it is just that WordPress exists in the middle of the continuum between content and functionality, part of it is the odd mix of users: you can have technically unaware users who you inadvertently empower to make bad decisions. It’s not their fault: it’s an over-permissive architecture. WordPress, in your own careful hands, can run brilliantly for years. In all the time I have run it (18 years now) my own sites have been fast, busy, stable, reliable: I have even run WP brochure sites for finance industry clients, and I have had full confidence in them. But if you’re not going to be in charge of it, don’t run it. Because really no amount of monitoring and security mechanisms can stop this eventually happening. Ultimately I have also decided I am not going to roll out any new WP sites that I have to maintain. But then (despite my admiration for Laravel) I am going to get out of using scripting languages for server side code at all. AI is going to make all internet-facing interpreters dangerous. It’s too large a surface and I don’t have the energy for php2shell Groundhog Day.
j45
Personally I can't wait for Wordpress to be revibecoded by super experienced devs.
LoganDark
`text-wrap: balance` looks terrible on these headings. At least use `pretty`.