Ok,

I'll Byte.

Composer, I understand why dependency management is important. In the same respect I understand marketing. Developer wise life could be easier. Wordpress wise it does not open up lots of new plugins as pretty much every conceivable plugin has already been done. What it results in ultimately is further loss of product control by Automattic. I'd not do it.

XML/RPC API. This is nothing new. Its simply a transport mechanism where WP apparently has been behind the curve. Yes, its important so WP installs can communicate better across services. XML/RPC will have a rather short life in terms of technology. The transport mechanism's console games have pioneered and will continue to refine are the future as they are binary, compressed, validated and deal with very complex datum in highly structured manners. The big question for PHP is can in handle it? Without multi-threading, no way. Its dead. Apache has no problem with it nor does IIs, Nginx, Linux, MS Server alonf with C#. PHP just does not have the umph without threading ability.

These digital transport (also secure transport) will be rearing their heads in 2-5 years. Which one becomes standard is very much up in the air right now. Since PHP developers keep their eyes on PHP they tend have no idea what is happening in the rest of the data technology universe. Sad but true.

Will WP become a data engine for other applications? Nope. Well... I cant say "nope". I can say, perhaps some relatively focused things where no money or least money wants be spent. Categories, text data in two formats and limited other capabilities along with procedural code doom it from whats coming in complex web applications. Again, people forget, PC/Mac OS are going as online operating systems. That means computers and devices become smart clients. Can you make Quickbooks online with Wordpress? No. Can you make Halo online with Wordpress. No.

As a "Framework" engine it cannot suit general purpose complex tasking. Symfony can. Its slower than snail snot. Again, no multiple thread ability within PHP and a general structure of how Object Oriented Code is managed by PHP are BIG hang ups as other languages and frameworks provide faster processings, smaller resource footprints and from word go were created for the tasks suited. This is why managed C# is now 300% faster than PHP. Mono is more capable and faster than any PHP framework going and happily runs under Linux or Mac OS as well.

WP is not ideal for a backend data service platform at least now. It'd take a ton of change to get there and in doing so would probably break its base usage now. Joomla thought similar, J! framework, J! CMS. Done nothing for them and J! framework is really good code, much more advanced actually albeit slower.

So I disagree, all fronts.

Automattic has a tremendous marketshare right now. The best move IMHO is sealing it. Making sure that it stays there and grows. Again IMHO that requires a restructure of its public assets to run more like a business and product (the volunteer scene) and towards not leaving the door wide open for others to exploit several really apparent weaknesses to anyone who's worked for "the sharks" in business and either get put asunder, bought out, or loosing the development community wordpress enjoys.

There are clearly people who have Wordpress Community best interests at heart but with a community of 200,000,000 installs are not the right people in the right places.