When having a few conversations a few years ago with enterprise devs, the React license was seen as a problem[0][1], and Angular wasn't, so the default path was

When having a few conversations a few years ago with enterprise devs, the React license was seen as a problem[0][1], and Angular wasn't, so the default path was from the top-down to go with Angular, for those I spoke to. This was also when Angular 2.0 was new and the comment was also "This is moving too fast". Once enterprise chooses a tool, that tends to stay the tool for that project, then all of the team is competent in the tool after a couple of years working with it. There's a critical time-frame when new competing tools win a geographical majority [2]. [0] Link to facebook announcing Reach license changes: https://code.fb.com/web/relicensing-react-jest-flow-and-immutable-js/ https://code.fb.com/web/relicensing-react-jest-flow-and-immu... [1] Link to short article on MIT-Patents license in reack. Takeaway: This has never been litigated before https://hackernoon.com/4-lessons-from-the-react-patent-license-controversy-3da3c4baf3a4 https://hackernoon.com/4-lessons-from-the-react-patent-licen... [2] Geographical majority http://www.businessdictionary.com/definition/geographic-monopoly.html http://www.businessdictionary.com/definition/geographic-mono... replace 'place' with 'technology tool'