In reply to Matt Mullenweg.

I am following Gutenberg development since first Beta version, and last 0.9 is starting to take shape of the plugin that at one point might be ready for merge to the core. If the metabox issues are resolved and all existing metaboxes continue to function as they are now, I will be a happy developer. TinyMCE had a rough development path when it was added for the first time, and any big change has to go through the similar trial by fire.

But, there is one major issue that has to be addressed as soon as possible: React license. WordPress embrace of open source and GPL is something that has to be preserved, and the React licence with the patents clause that is all but honest and open goes against everything WordPress stands for. Gutenberg needs to go away from React as soon as possible to maybe some React clone that is truly open source or to some other framework like Vue. This is not only the question of WordPress using some 'fishy' licensed library, it is important because WordPress is used by a lot of companies that might get into legal troubles with Facebook in the future that will end up stranded because of the license. I am not a legal expert, but everything I have read so far related to React license, opinions from Apache Foundation and more, tells be that WordPress core must stay away from Facebook's React.