@Kevinjohn Gallagher -

I wasn't particularly upset about your original article, and thought you raised some valid points concerning a subset of enterprise features where WordPress doesn't stand up particularly well, that we need to address.

Reading your reply, here, however, I can understand why people are upset. You claim that you're just saying "there are better choices in some case", but really, you spent half that post trashing a CMS that many of us enjoy and find effective. Case in point: you're doubling down here by repeating the myth that WordPress is just a blogging tool. It's not the right CMS for your clients? So be it. WordPress wasn't design for the blind or visually impaired, you're correct (something a good canonical "visual impairment" plug-in should solve). It's not a CMS? In the "penis size" contest I guarantee you that our clients, who use WordPress as a CMS and enjoy it, can easily match yours. You're just instigating. It is a CMS, and in my fairly diversified CMS experience, a really good one. Not perfect, and not for everyone.

In other words, I don't think anyone is upset that you're no longer promoting WordPress. Outside of the web developer bubble no one probably cares about or is influenced by your decision (other than your clients), and inside the bubble I don't think anyone is switching platforms based on your post. People are upset that you're crapping on WordPress on the way out the door.

For the record, I agree that we're "refining" and changing the up the UI side of things too often, mostly because it disrupts plug-ins that can solve things like disability concerns. However, that's not detracting from functional advances. With few exceptions, the volunteers or paid core developers that focus on UI would not be spending their time on API type functionality or a multilingual module, and the code heads are not spending much energy on the UI changes.

We'd still like to know which CMS, exactly, solves all of your problems.

You told me that you're in favor of a rapid release cycle, but other open source solutions that cater to some of your bigger concerns have releases of any significance maybe once every 2-3 years. There seem to be some respectable commercial solutions available these days, but you're also more or less trapped by what they offer.

The reality is that there *is* a trade off between very deep testing for disability compliance and browser backwards compatibility testing (especially if you want it at the *beta* phase) and rapid release cycles. Theoretically it can be solved with more man power, which is why @JJJ is absolutely right.