3 ms·

When the deprecation was originally announced I basically just decided to sever from Angular all together. The "migration" practically involved rewriting pretty

by pram 5y ago

When the deprecation was originally announced I basically just decided to sever from Angular all together. The "migration" practically involved rewriting pretty much everything anyway. The new thing is surely technically superior, but it just left me very bitter. I learned my lesson!

NicoJuicy 5y ago
AngularJS is a different framework. They are not the same and i think that was very clear from the start. ( I've written webapps in both AngularJS and Angular)
- pram 5y ago
  Yes obviously. Angular started as "Angular 2" (as in version 2 of AngularJS) and didn't exist until like half a decade after AngularJS. You think it was 'clear from the start' that they'd just abandon AngularJS? Why would anyone have used it?
  - hnbad 5y ago
    Not only that, Angular 2 spent an extremely long time in beta with several major changes (the original architecture was built around "Object.observe", which was a proposed language feature that was canned after Google tried to implement it and realized there was no way to make it efficient). Users looking into Angular were actively discouraged from using Angular 2 prior to its stable release despite AngularJS being clearly a dead end and even after the dust had settled there was no clear upgrade path from AngularJS to Angular 2. By comparison React has provided automated code migration scripts for every breaking change and continuous to support class-based components and lifecycle events despite most of the ecosystem having moved on to function-based components and hooks. Say what you will about React, Facebook or Meta, but at least there have always been clear upgrade paths that didn't involve rewriting the entire application from scratch.
- deleted 5y ago
  [deleted]
- simiones 5y ago
  It was clear from the start of Angular 2, not from the start of Angular (later renamed AngularJS).
arnvald 5y ago
Same experience here. Despite tools provided by the Angular team, the migration was really, really painful. I spent a significant amount of time moving a large AngularJS app to Angular, and despite all the effort we were still far from completing it when I left the company. These days I use Vue or React instead.
JamesSwift 5y ago
Ive migrated several apps to angular 2 and assuming you got to angular 1.6 (or even just 1.4 with components) first, the rewrite is no big deal unless you heavily leverage specific things (root scope, some directive stuff, some template cache stuff). Especially with ngUpgrade available, I never found it terribly hard, though it did take time.
bradleyjg 5y ago
You should have talked to an old GWT dev before starting down the road of using a Google maintained framework.
- hsbauauvhabzb 5y ago
  I’ve seen gwt. It smells bad, but it seems supported still. Can you elaborate on your comment so I have conversation points next time I deal with that team?
  - bradleyjg 5y ago
    Google hived off support to an open source foundation about a decade ago. It wasn’t well supported even before that for several years (I remember at one point they went through and closed all the open issues as Assumed Stale). They also loved to pivot best practices every year and stop developing the code that supported last year’s best practices.
    - hsbauauvhabzb 5y ago
      As an outsider that’s an extremely insightful and not something I’d ever learn from official documentation. Thank you for your response.
ldiracdelta 5y ago
This is why I never even considered flutter development. Who knows when the platform will just die on the vine.
tdekoekkoek 5y ago
why would you be bitter since they just improved the platform. It wasn't hard to learn the migration and AngularJS needed to be let go. Angular is every bit as good as other alternatives.
Alex3917 5y ago
> The "migration" practically involved rewriting pretty much everything anyway. I used the 10-step process outlined here and it was pretty straightforward: https://codecraft.tv/courses/angularjs-migration/overview/introduction/ https://codecraft.tv/courses/angularjs-migration/overview/in... There were definitely methods in the components that needed to be moved into services, but there wasn't really much rewriting per se. FWIW the first five steps, in terms of upgrading the AngularJS app so that it used isolated components instead of nested scopes, was more time consuming than actually porting the modernized AngularJS app to Angular.

by pram 5y ago

NicoJuicy 5y ago

AngularJS is a different framework. They are not the same and i think that was very clear from the start. ( I've written webapps in both AngularJS and Angular)

pram 5y ago
Yes obviously. Angular started as "Angular 2" (as in version 2 of AngularJS) and didn't exist until like half a decade after AngularJS. You think it was 'clear from the start' that they'd just abandon AngularJS? Why would anyone have used it?
- hnbad 5y ago
  Not only that, Angular 2 spent an extremely long time in beta with several major changes (the original architecture was built around "Object.observe", which was a proposed language feature that was canned after Google tried to implement it and realized there was no way to make it efficient). Users looking into Angular were actively discouraged from using Angular 2 prior to its stable release despite AngularJS being clearly a dead end and even after the dust had settled there was no clear upgrade path from AngularJS to Angular 2. By comparison React has provided automated code migration scripts for every breaking change and continuous to support class-based components and lifecycle events despite most of the ecosystem having moved on to function-based components and hooks. Say what you will about React, Facebook or Meta, but at least there have always been clear upgrade paths that didn't involve rewriting the entire application from scratch.
deleted 5y ago
[deleted]
simiones 5y ago
It was clear from the start of Angular 2, not from the start of Angular (later renamed AngularJS).

arnvald 5y ago

Same experience here. Despite tools provided by the Angular team, the migration was really, really painful. I spent a significant amount of time moving a large AngularJS app to Angular, and despite all the effort we were still far from completing it when I left the company. These days I use Vue or React instead.

JamesSwift 5y ago

Ive migrated several apps to angular 2 and assuming you got to angular 1.6 (or even just 1.4 with components) first, the rewrite is no big deal unless you heavily leverage specific things (root scope, some directive stuff, some template cache stuff). Especially with ngUpgrade available, I never found it terribly hard, though it did take time.

bradleyjg 5y ago

You should have talked to an old GWT dev before starting down the road of using a Google maintained framework.

hsbauauvhabzb 5y ago
I’ve seen gwt. It smells bad, but it seems supported still. Can you elaborate on your comment so I have conversation points next time I deal with that team?
- bradleyjg 5y ago
  Google hived off support to an open source foundation about a decade ago. It wasn’t well supported even before that for several years (I remember at one point they went through and closed all the open issues as Assumed Stale). They also loved to pivot best practices every year and stop developing the code that supported last year’s best practices.
  - hsbauauvhabzb 5y ago
    As an outsider that’s an extremely insightful and not something I’d ever learn from official documentation. Thank you for your response.

ldiracdelta 5y ago

This is why I never even considered flutter development. Who knows when the platform will just die on the vine.

tdekoekkoek 5y ago

why would you be bitter since they just improved the platform. It wasn't hard to learn the migration and AngularJS needed to be let go. Angular is every bit as good as other alternatives.

Alex3917 5y ago

> The "migration" practically involved rewriting pretty much everything anyway. I used the 10-step process outlined here and it was pretty straightforward: https://codecraft.tv/courses/angularjs-migration/overview/introduction/ https://codecraft.tv/courses/angularjs-migration/overview/in... There were definitely methods in the components that needed to be moved into services, but there wasn't really much rewriting per se. FWIW the first five steps, in terms of upgrading the AngularJS app so that it used isolated components instead of nested scopes, was more time consuming than actually porting the modernized AngularJS app to Angular.