[kreck]

We started with Angular.js (1) and then migrated all our projects to 2+ as soon as it left beta. At this point we also evaluated react and later took a look at vue. The main reason why we stick with Angular are the baked-in best practices and the tooling (angular-cli). Especially if you work on larger projects and have several people working on them, (opinionated) Angular simply makes your life a lot easier. With react (and vue) you have to make so many small decisions when setting up your project, that especially less experienced developers are tempted to make potentially "bad" design decisions (e.g. testing framework, bundling, routing, state management, ... you name it).

[chrisco255]

At this point in React's lifecycle, there are one or two top choices for each category you mention (ie MobX vs Redux, Jest vs Jasmine, etc) for folks worried about making "bad choices" well I would ask, what makes a choice bad? Is it that a particular state management library is a bad fit for your application? In that case, where it's possible that a library is a bad fit, then how can it be that a one-size-fits-all framework is going to not equally have potential to be a "bad" choice, except with a lot more buy in and difficulty to change down the road?