In reply to Ryan Hellyer.

I agree with Vladimir.

A forward looking, fuck backwards-compatibility, version with a minimum recommendation of the latest scripts and tech stack is an interesting new world for WordPress. Without much thought, I can envision a WP version much like Ghost but with a CMS-focused mandate. So pages, custom post types, ecommerce, etc. Much of WP's woes come from the insistence on backwards compatibility. Catering to people who either don't know how to maintain their sites or refuse to is holding us back!

With the advent of social media and the big F eating up the world's traffic, it has become quite clear that in order to succeed on the web, you need to know your shit! Pandering to clueless end users is not doing WP any good.

Remember when WooThemes broke backwards compatibility? Pretty sure some of the new and exciting stuff they are working on now would not be possible if WooCommerce was lugging around all that legacy code.

All this Rest API/Calypso/JavaScript/SPA talk wouldn't be as necessary if WP was centred around keeping abreast with the latest technologies and not placing too much emphasis on supporting outdated technologies!

Sure, WP does not have to be at the bleeding edge of web technology use. I for one have no problem with WP being a PHP reliant CMS; see PHP sucks but such nonsense as supporting a PHP version that has been EOLed makes me wonder why one would want to invest in WP for their business. Yes, I can use the latest version but all that legacy code affects my site regardless of how polished and up to date my server and WP instance is.