I put &quot;enterprise grade&quot; in quotes on purpose. React stack (not React alone) being used successfully by a 9-5 Java or C# shop is not something I&#x27;d be willing to bet on.<p>Sure it&#x27;s simple as far as hello world apps go, but once you start adding state management, routing, etc. you start seeing that it diverges from conventional architecture approaches. Not saying that&#x27;s  necessarily bad but it does not mesh well with enterprise development - I hope you understand what I mean by this.<p>And tools that help ensure consistency&#x2F;quality in that kind of environment like TypeScript are very unsatisfying with React and various libraries, for eg. look how tedious Immutable.js typed records are, and check out typings for Redux related libs - bunch of any typed parameters and return values. Flux basically has no support outside of React and it wouldn&#x27;t even run on Windows last time I checked.<p>So like I said - it depends on the context - if we&#x27;re talking a bunch of JS frontend devs I&#x27;d say go for React if it fits what you&#x27;re trying to do. If you&#x27;re a .NET&#x2F;Java shop Angular 2 is probably going to be a better fit, patterns like DI, OOP, etc. are all at the core and it&#x27;s a full stack framework you just pick up and follow it&#x27;s conventions&#x2F;best practices&#x2F;design decisions - way less decisions than React and way better docs (for the stuff not included in React I mean, React documentation is decent).