14 ms·

> What is to be done? ... Consider non-microlib architectures What about what happened with Angular (1), the 3rd library on your list? That whole framework was

> What is to be done? ... Consider non-microlib architectures What about what happened with Angular (1), the 3rd library on your list? That whole framework was deprecated in favor of Angular (2). Additionally, the list of front-end libraries given doesn't really reflect the landscape front-end devs have traversed. Years ago, I remember working on an app that heavily relied on YUI around the time that library was shutdown. I also heard stories about how ExtJS 4 wasn't backwards compatible. I'm not sure I buy into the author's thesis about the reason for front-end fatigue.

reitanqild 8y ago
There's a clear upgrade path (with tooling) between Angular.js and Angular 2, 4, 5, 6. There's now also https://update.angular.io/ https://update.angular.io/ to help.
- patorjk 8y ago
  Angular 1.x is not listed in https://update.angular.io/ https://update.angular.io/. Additionally, there was no initial update path between Angular 1 and Angular 2 until the community cried foul. It's been a while, but after they finally released an Angular 1 to Angular 2 bridge, I read several tutorials and books that discussed the upgrade path but said to absolutely not use it in production. It would kill the performance of your app. That sort of made the value of an Angular 1 to Angular 2 bridge pretty weak. If one were to migrate to Angular 2, it would seem more time efficient to just to start fresh rather than spend time on a wonky bridge between the two frameworks.
  - reitanqild 8y ago
    At AngularConnect last year I now migration of large applications was a topic and if you are interested I think it should be available online. Also: angular.js isn't dead, it is just stabilized. Yes, no more features (from Google) but it should be safe to use and also I think they signalled quite clearly that they would be happy to let the community pick it up.
emodendroket 8y ago
I feel like Angular was reaching escape velocity and becoming the one thing to learn and just as it was happening they announced Angular 2, which was originally going to have no upgrade path and no two-way binding (arguably the killer feature), out of performance concerns that weren't a problem for the vast majority of use cases. Even after they backtracked on a lot of this it was too late; they had forever tarnished their own product. I really loved Angular 1 precisely because it had everything you needed, more or less, built-in.

reitanqild 8y ago

There's a clear upgrade path (with tooling) between Angular.js and Angular 2, 4, 5, 6. There's now also https://update.angular.io/ https://update.angular.io/ to help.

patorjk 8y ago
Angular 1.x is not listed in https://update.angular.io/ https://update.angular.io/. Additionally, there was no initial update path between Angular 1 and Angular 2 until the community cried foul. It's been a while, but after they finally released an Angular 1 to Angular 2 bridge, I read several tutorials and books that discussed the upgrade path but said to absolutely not use it in production. It would kill the performance of your app. That sort of made the value of an Angular 1 to Angular 2 bridge pretty weak. If one were to migrate to Angular 2, it would seem more time efficient to just to start fresh rather than spend time on a wonky bridge between the two frameworks.
- reitanqild 8y ago
  At AngularConnect last year I now migration of large applications was a topic and if you are interested I think it should be available online. Also: angular.js isn't dead, it is just stabilized. Yes, no more features (from Google) but it should be safe to use and also I think they signalled quite clearly that they would be happy to let the community pick it up.

emodendroket 8y ago

I feel like Angular was reaching escape velocity and becoming the one thing to learn and just as it was happening they announced Angular 2, which was originally going to have no upgrade path and no two-way binding (arguably the killer feature), out of performance concerns that weren't a problem for the vast majority of use cases. Even after they backtracked on a lot of this it was too late; they had forever tarnished their own product. I really loved Angular 1 precisely because it had everything you needed, more or less, built-in.