4 ms·
> The "decline" of angular hasn't happened Not the decline but I guess before migration to 2.0 a lot of Users will reevaluate if they will use 2.0. I doubt tha
by merb 10y ago
> The "decline" of angular hasn't happened
Not the decline but I guess before migration to 2.0 a lot of Users will reevaluate if they will use 2.0. I doubt that only a few already migrated to Angular 2.
Tooling gets better but in Angular 1 there are a lot of ways to create a project and minify it etc. On Angular 2 a lot of documentation is still missing.
We have a big angular 1 app but I'm not sure if we will migrate to 2.0.
I also think that once an Application get's really large it's painful to use a framework that isn't tailored to your needs anyway.
- was_boring 10y agoAt my job we have a large angular application, and several smaller react + redux + flavor of the month. We will never move to angular 2, not because it's not a good idea, but because we don't need it. One of the most expensive lessons of these framework wars (in my opinion) is that the vast majority of problems don't need them or warrant the complexity. Angular everywhere is the wrong approach, just as react everywhere is wrong. Now if only I could convince the front-end engineers that their static form and homepage doesn't need react + redux + Babel + webpack.