As if anyone stuck on AngularJS has been upgrading or needing support to begin with. Simply updating from 1.2 to 1.5 breaks most apps.
AngularJS support is ending, and developers can migrate to Angular
11–20 of 54 posts
Re: AngularJS support is ending, and developers can migrate to Angular
#12When 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!
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)
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?
Re: AngularJS support is ending, and developers can migrate to Angular
#13Earlier quoted context omitted.
> I'm a big Angular fan, even if I tried React, I highly prefer Angular for being more strict, complete and imho more suited for very big projects. I agree, I just moved us to Angular 13 and I love every second of it. I've worked on React projects but will take Angular any day of the week.
Having worked with both, react much much less, but more recently, I find react just simpler to get stuff done with. Angular has a pretty rigid structure that I felt required more files and code (even if you just use the ng CLI to code gen the initial component or service) to do the same thing. Obviously the batteries included nature of Angular is nice. But otherwise I felt less burdened by the amount of code I need t…
Imo react is simpler to get stuff done with up until a certain point. Every large react project I’ve contributed to, or adopted, had the same overhead you described of Angular. Further, each had built custom abstractions due to the nature of how integration works with react. Some apps were fine, some had 1000+ line state files, 1000+ lines of hooks management before a render, weird ways of using context or passing props.
Today we still prototype mostly with react. It’s easier to staff junior devs around and empowers them when it comes to trivial logic with cool UX.
Any large scale work, or prototypes going to prod, do so with Angular. Where we’re confident in the Sr level engineers writing that code.
Re: AngularJS support is ending, and developers can migrate to Angular
#14"Clarification: AngularJS and Angular are different frameworks. The announcement for end of life is for AngularJS that Google released in 2010. Angular is in active development and growing. Exciting big changes coming in 2022!"
> Originally, the rewrite of AngularJS was called "Angular 2", but this led to confusion among developers. To clarify, the Team announced that separate terms should be used for each framework with "AngularJS" referring to the 1.X versions and "Angular" without the "JS" referring to versions 2 and up. -- https://en.wikipedia.org/wiki/Angular_(web_framework)#Naming Well, nice try I guess. Still, they do say that "Namin…
Can't quite put my finger on it, but I just can't shake off the feeling that your quote from wikipedia is implying blame on the "end user" devs for the confusion, instead of the team for naming things so badly.
> Those stupid developers don't realize that AngularJS and Angular2 are two completely different frameworks! Okay, I guess we need to make it now VERY CLEAR that they are different. How about AngularJS and Angular? Sounds good, right? Now it should be clear to everyone the two are different frameworks.
Switched from AngularJS directly to Vue.js after the months of confusing messaging, no regrets, Vue.js is what Angular2 should have been, in my opinion.
Re: AngularJS support is ending, and developers can migrate to Angular
#15When 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!
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)
[deleted]
Re: AngularJS support is ending, and developers can migrate to Angular
#16When 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!
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.
Re: AngularJS support is ending, and developers can migrate to Angular
#17As an ex-AngularJS developer, who worked on porting a LARGE app to Angular - if you're in that boat, look into just rewriting in Vue. It's similar to AngularJS (more so than Angular) but with some extra niceties.
Re: AngularJS support is ending, and developers can migrate to Angular
#18When 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!
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.
Re: AngularJS support is ending, and developers can migrate to Angular
#19Earlier quoted context omitted.
> Originally, the rewrite of AngularJS was called "Angular 2", but this led to confusion among developers. To clarify, the Team announced that separate terms should be used for each framework with "AngularJS" referring to the 1.X versions and "Angular" without the "JS" referring to versions 2 and up. -- https://en.wikipedia.org/wiki/Angular_(web_framework)#Naming Well, nice try I guess. Still, they do say that "Namin…
> "Naming things" is one of the two hard problems in computer science. For those who don't know, the other two are: Cache invalidation, and off-by-one errors.
1 instead of zero index based languages such as e.g Julia therefore remove a LOT of cognitive overhead.
Re: AngularJS support is ending, and developers can migrate to Angular
#20When 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!
You should have talked to an old GWT dev before starting down the road of using a Google maintained framework.