But it is easier if they all come in one big package, with one 'recommended' way to handle it all. There are two ends of the spectrum that each library/framework aims at - hyper customisability for React and ease of development for Angular 2. I can see people who don't want to shop around for a form validator, etc. etc. happily moving to Angular 2 (and even those who would shop around, if it turns out to be the best design - yet to be seen).
Or they could just pick up the industry defaults for React projects - Redux for state management and react-router for, uh, routing. This is what is already happening.
Besides, you miss a larger point. There's only sense submitting to the yoke of a framework's "opinionated defaults" if those defaults are actually good. From what we've seen of the release candidate, NG2's... aren't.
Or they could just pick up the industry defaults for React projects - Redux for state management and react-router for, uh, routing.
As an outsider who hasn't used React at all yet, it seems hard to keep up with that. It's hard enough to keep on top of everything else we have to deal with already—build tools (Gulp, Grunt, Webpack etc.), test frameworks, CSS preprocessors (SASS, LESS, Stylus, PostCSS) and so on without the added complexity of keeping up to date on the latest React router/state manager etc.
0
u/[deleted] Sep 15 '16
[deleted]