|
|
|
|
|
by zxcvcxz
3693 days ago
|
|
React is eating Angulars lunch when you look at the amount of large enterprises that choose react over Angular. Part of the problem with Angular that no one seems to care about is that Angular 2 was such a big change from Angular 1 it forced companies that depended on Angular 1 to do a complete re-write. I was an Angular 1 dev and Angular 2 caused me to abandon Angular altogether. Angular also adds more abstractions on top of JS which is unnecessary and can cause unexpected behavior when transpiled. |
|
Most companies are doing the responsible thing and holding off on worrying about migration until Angular 2 stabilizes more. Even if one wanted to do a complete rewrite due to poor Angular 1 app code, one can then evaluate all options from scratch and choose the best option for their app.
Every library adds abstractions on top of JS - React is no different with your complaint of unexpected behavior.
This reads as an overly emotional post without applying engineering - "this sounds too hard so I'll just run away to another solution" is the vibe I get.