In reply to Matt.

I absolutely agree that we can't assume that React's license will stay the same, this is why the framework agnostic approach is so important. Whatever framework ends up being used behind the scenes, we need to work on the premise that we may need to seamlessly swap it out for something else in the future.

As Matt mentioned, this approach lets us treat many frameworks as officially supported options. Regardless of what Core uses internally, developers can create in whatever fashion they're most comfortable with, forcing people into one particular method has never been a Core philosophy, we're not about to start now. 🙂