In reply to Joe Hoyle.
The discussion by itself is just an elitistic discussion disconnected from the wordpress grass roots. It is nice that in the end the automattic developers and their VIP partner will be able to drop the names VUE or REACT or whatever, when they need to sell something to prospecting client. for 99% of wordpress developer the only question they should ask (they do not follow the discussion at all so they do not even know about it to actually ask), is how easy will they be able to move the pricing above the product picture in their woocommerce site, and neither of the frameworks are likely to make it easy.

The power of wordpress comes from the fact that any site owner that wants to rearrange the category list in the “meta” section of a post display, can google it, find some snippet, copy paste into the theme’s function.php and he is done. Can you see any non full time developer being able to set the tool chain to work with react or vue or whatever?

It is not like JS standardization is bad, it is actually a very much needed thing, but the original point of the whole discussion which was about mimicking PHP APIs for translation, hooks etc in the JS world was very fast highjacked to serve as a platform for frameworks wars, without even giving a lip service to the original goal. So @joe how exactly having react or vue or whatever you prefer will help with letting me “remove_action” on one of the theme actions, or set mine to run before it?

Isn’t it bad enough to have the backbone framework in core? why do we need two frameworks? why can’t wordpress just solve the problems associated with backbone instead?

As for react, I am with @peter, whatever are the technical merits of the framework, if used, the wordpress license will have to change to “GPL as long as you do not sue facebook”