4 ms·
The prevailing opinion on HN seems to be that React is great, and monolithic frameworks are bad bad bad - especially Angular. On a recent project I started for
by jinder 9y ago
The prevailing opinion on HN seems to be that React is great, and monolithic frameworks are bad bad bad - especially Angular.
On a recent project I started for a client, we did a full evaluation of React + Redux vs Angular 2/4 and NGRX.
Angular's first-class support for TypeScript, and RxJS is incredible when leveraged properly. Integrate this with NGRX for Redux style state management, and you get a compelling solution that is miles ahead of the React/Redux combo if you can get over the template syntax (instead of JSX) and the opinionated flavour of Angular.
It's difficult to offer an alternative opinion in the HN echo chamber, but we're having excellent results using Angular CLI + Angular 4 + RxJS + NGRX. It's worth the steeper learning curve, IMHO.
- Stoids 9y agoTo add to that, most new React/Redux projects are settling on the same technology decisions as the Angular team. TypeScript/Flow, RxJS for async/effect handling (or Sagas). React vs Angular is pretty negligible at this point. They are both component focused frameworks and that's the important paradigm and shared quality amongst all these frameworks. Anyone who understands the architecture of one should be able to learn the other relatively quickly. I haven't personally used Angular 2/4, but it looks like a really solid and opinionated solution. Some people don't want to spend 3 days researching thunks vs sagas vs observables, so I'm glad something like Angular exists.