I see that "React just seemed like the better choice over Angular due to their direction" statement a lot recently.
Can you go into detail on why React is apparently a replacement of Angular?
I always had the notion that React and Angular solved two different problems. Angular is a fleshed out, full MVC framework, while React only acts primarily as the "V". Having dabbled in both, If you want React to do the same thing as Angular, there is A LOT of "puzzle-piecing" that is required. And that can seem like overkill when Angular is complete and ready to go.
Can you go into detail on why React is apparently a replacement of Angular?
Consider it from the perspective of a CTO/Lead Dev/Decision maker who has a single page app to build.
On a practical level since angular 2 was announced it's been difficult to justify building an application with 1.x because it has a very obvious expiry date after which you have to start rewriting code and retaining devs.
Angular 2 hasn't been stable enough for production systems until recently. It also doesn't have the same level of community support as 1.x so there's a lot more work to be done until the community releases resources (tools, libraries, documentation, guides etc.).
Meanwhile you've still got a SPA to build and neither of the Angular options seem inviting.
React (+ whatever) is stable, has a good community and lots of resources. It's also a new hotness that all your devs are eager to try out. That's why I started using React. Despite knowing Angular pretty well I couldn't make a compelling case to the CTO or myself that Angular in any guise was a better long term option for our systems vs React (and in my case Flux).
0
u/[deleted] Sep 15 '16
[deleted]