The dire state of WordPress
A (reasoned) criticism of the architecture of WordPress, and how it should be fixed.
Similar Posts
Polish your code
If we can polish a turd, we can polish our code. Your code doesn’t have to be perfect. In fact, it probably won’t be. But it should be clean, documented, organized, and use proper syntax. It should be polished. Polishing your code today will make you a better developer, and you’ll thank yourself when you…
WooCommerce Function of the Week: wc_price
The wc_price function solves your WooCommerce price formatting problems. Using it means you can ignore the WooCommerce price settings.
BobWP’s Woo Snippet for the Week of March 27
WooCommerce 6.4 RC 1 📦 Blocks and Admin 🔌 Time to Retire ZeroClipboard ⚠️ Clients in a Candy Store 🍬 Sustainable Woo? 🪴 Zach Stepek, Carl Alexander, Till Krüss, and JJJ 🎙️
2 Comments
Comments are closed.
I get much of what the author is saying, but I also think there’s not much stopping plugin and theme developers from changing their practices themselves. Also, I don’t think a theme architecture like twenty twelve is unorganized spaghetti code at all. It may not be what the author thinks its best, but it’s not unorganized in my opinion.
The Hacker News discussion on this is entertaining as well https://news.ycombinator.com/item?id=5407879
I think a commenter there maybe nailed it: “WordPress is the worst CMS — except for all the others”. What core developer is satisfied with the codebase? None. If they were, they’d quit contributing. The platform is positively evolving in the best way its contributors know how — with time and energy.
Every now and then there will always be someone with an elitist pov to How It Should Be Done. Even though he has very valid points his rant shouldn’t have been about the dire state of WordPress, but more-so about how he thinks the software evolution of WordPress should’ve went down and what he could’ve done to to help.