I would argue, as others have done, that the author is correct in his points, but a rewrite would throw away the main advantages of using Wordpress over alterna

I would argue, as others have done, that the author is correct in his points, but a rewrite would throw away the main advantages of using Wordpress over alternatives. There are tons of successful initiatives to create a 'better' CMS. But they suffer from a lack of ready-made modules and a lack of developers 'fluent' in these systems. In the end, it's about the right tool for the job, and unfortunately Wordpress is often the right tool despite all its issues. If we are caught in the Wordpress ecosystem, then perhaps the best thing to do is to 1) contribute to making it (slightly) less bad, and 2) create best practices for theme and module development, improve documentation, etc. Why anyone would want to do that is beyond me though, but I deeply respect those who do so, instead of writing their own shiny and clean solution. As for me, I started with Wordpress, no clue what I was doing, and very basic knowledge of programming. Wordpress worked, and I made a living. Then I 'upgraded' to Drupal, and loved its flexibility and powerful modules, worked out my own 'admin interface' and happily used this base system for many complex sites. I made a slightly better living. Then I got into Rails development. I learned about 'environments', TDD, MVC, and so on, and soon realized that Drupal has many, many drawbacks. (And, as an aside, to configure and maintain these Drupal sites and the interaction of its powerful modules requires a skill and mindset that is about equal to writing (basic) Rails sites or using other frameworks. Except that in Drupal, instead of version-controlled code, you have one giant database and you click click click forever instead of writing a few lines of code.) Now, I'm doing (in the eyes of many front-enders) weird shit like learning Clojure and Node.js to see what I can do with it, playing with a bunch of different frameworks and CMS offerings, and trying out these new-fangled front-end-heavy buzzwords like Angular, Backbone and Ember. And yet, if a client has little money, or if I need something quick, I often still opt for Wordpress. It hits the sweet spot. If a client has more money later, well, then I could look into using a framework and rolling out something myself. Drupal, despite it's deceptive initial attractiveness, is almost never a good solution. I use Wordpress mostly for the client. In the same way that I've inherited Wordpress sites after a developer disappeared, or if a designer couldn't figure it out, I assume others might inherit my projects. If the client has little budget, I really don't want them to be forced to hire expensive Drupal developers, or 'proper' developers who can figure out 'obscure CMS <x>'. But generally I try to stay away from those clients, if I can help it.