@Terence Milbourn

You are right, and the point of my wish list article cited here is that WordPress needs a lot more work that can't be fixed with plugins as some have suggested. There are plugins for WP to replace the whole admin side, but that ain't the point. It is clear that there are features that must be part of the core.

I don't care about the look of the admin screens and if they are green or black or red. I don't care about theme customizer that is next to useless for most purposes. I don't care about searching WordPress themes repository. And most people that use WP for business don't either. They need a solid core that has all the things to deal with data, they all use custom themes they don't plan to change for year or more, and they need usable admin screens that can do what they are suppose to, regardless of their color or pixel positions.

I know that features I talked about are not easy to do, and that is exactly the point. Some of them are long overdue for rewrite and are becoming a laughing matter when WP is considered, like useless search.

My point from all this, is that people leading WordPress Core development need to take a long hard look at all the problems WP has, at all the features that need to be in the core, and to make a plan for a long development cycle that will cover most of that. Making new WP every 3-4 months is a bad decision, and it needs to stop for the sake of WordPress. Take a year and give us better WordPress. Better WP core will bring better plugins and themes, and that will give us better websites.

And with any open source project, if they don't, someone else will. I would hate to see parallel WP development, but it can happen if the current development trend continues.

Look at the adoption rate of latest 3 WP versions and you will see that current development cycle is bad, and that most of the users will not upgrade to a WP that brings nothing that important.

Milan Petrovic