7 ms·
AngularJS support is ending, and developers can migrate to Angular
- SlowAndCalm 5y agoIt's strange to think I was working on AngularJS and Flash apps at the same time. Flash feels like it was a millennia ago, whilst AngularJS feels very recent. Maybe because AngularJS's successor keeps it's name fresh in my mind?
- hericium 5y ago"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!"
- Karellen 5y ago> 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 https://en.wikipedia.org/wiki/Angular_(web_framework)#Naming Well, nice try I guess. Still, they do say that "Naming things" is one of the two hard problems in computer science.
- purerandomness 5y ago> "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.
- The_rationalist 5y ago1 instead of zero index based languages such as e.g Julia therefore remove a LOT of cognitive overhead.
- planb 5y agoNot using indices at all when iterating whenever possible completely eliminates the cognitive overhead.
- The_rationalist 5y agoYes except when it's not possible or require non-reusable custom iterators.
- serial_dev 5y agoCan'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.
- pram 5y agoWhen 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 agoAngularJS 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 agoYes 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 agoNot 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]
- 5y ago
- davide_v 5y agoTotally correct to discontinue the old AngularJS imho. Google, years ago, made one of the best choice adopting TypeScript for its new framework, Angular. I used to code in both AngularJS and Angular, and the improvement between the two is huge, thanks also to TypeScript. 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.
- EMM_386 5y ago> 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.
- aawalrik323 5y agoHaving 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 to write and read in react. RxJS is nice though and testing via dependency injection as long as your app isnt a horrible mess and has good decoupling.
- ramoz 5y agoImo 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.
- trixie_ 5y agoAs 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.
- impostervt 5y agoAs 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.
- paaaaaaaaaa 5y agoWe were very close to doing the same but then we discovered Svelte. Svelte has been a dream to work with so far.
- tdekoekkoek 5y agoI worked on AngularJS and moved to Angular ever since 2+. It is a great platform and actually similar to Vue in some respects. No reason to abandon Angular although Vue and others are also good.
- bdcravens 5y agoAngular is so different some AngularJS that it's really a different framework. At that point, as long as you're switching to a new framework, you should assess them all equally according to your needs.
- hbn 5y agoI work in Angular, and yeah it's worth noting that Angular can be kind of exhausting to keep up with. While they haven't done as major of a breaking change as the jump from AngularJS to Angular 2 since then (I honestly don't even know why they have the same name, other than cause people knew the name), their release cycle is pretty fast, and there's entire websites dedicated to giving you bullet-point checklists of all the things to change/check as you upgrade from version to version. I'm only a tad familiar with Vue, but it seems like you wouldn't have as many curve balls thrown at you by committing to that framework. Which makes sense with it being essentially 1 guy's project, rather than a giant like Google (who famously is not one to care for backwards compatibility)
- bob1029 5y ago
- jokoon 5y agoI was asked to use angular in a java job. I was going crazy with all the files you need to have for a small project. It's like all the horrible sides of OOP and abstraction, but on steroids.
- commandlinefan 5y agoI have the same problem with Angular that I have with Spring - nobody can actually articulate what problem these frameworks are trying to solve (other than the problem of there not being a framework?). They both feel like tons of overhead with zero actual functionality.
- nsxwolf 5y agoModern Spring framework (annotation driven, no more XML config hell) offers a lot. Spring Boot is one of the easiest ways to start a backend Java app, microservice or monolith. You get ORM, a web framework, dependency injection, messaging, and a whole lot more just by including the modules you want. You can learn the basics in an afternoon of reading documentation. The major IDEs have very good plugins. A legacy Spring app can be absolute hell, though. That said, Angular (1.x) was the worst professional experience of my life. It was the only technology I absolutely could not learn enough to get comfortable with, despite working with it daily for over 2 years. Non-stop banging my head against my desk. That job caused real depression, burnout, health problems.
- commandlinefan 5y ago> You get ORM, a web framework, dependency injection, messaging But you can get all that stuff without Spring, too. And Spring adds another layer in between you and the ORM, the web framework and the messaging framework - a layer that's heavily reflection-based and makes a ton of undocumented assumptions about how things are set up and throws cryptic error messages when those assumptions are violated.
- nsxwolf 5y ago
- dorsdag 5y agoOur company saw the writing on the wall several years ago and completely ditched AngularJs and moved to React. It was wildly successful - after the whole project was rewritten there was dramatically less code, even though we added tests and new features along the way. https://www.singlewire.com/blog/development/react-migration https://www.singlewire.com/blog/development/react-migration Just doing it piece-by-piece was a really good strategy, instead of a stop-the-world rewrite.
- qwerty456127 5y agoAren't these too different to just "migrate"? Isn't it going to be more of a rewrite?
- JamesSwift 5y agoNo, you can either run them side by side (ngUpgrade) or move to angular 2 incrementally by first upgrading to angularjs 1.6 then going to angular 2. From there its a matter of moving up the angular 2 upgrade path. The initial rollout of angular 2 vs angularJS was a confusing shit show (and will bite anyone getting into angular brand new as they hit constant google results for one angular when they want the other), but the upgradability is a case study in how to do it right in my opinion. They really made it accessible for anyone to move an app over.
- polyterative 5y agoIn the last five years, I have used Angular2+ full time. RxJS is the greatest superpower ever. Totally loving it.
- aluminum96 5y agoFor those who don't know, it's possible (and encouraged) to migrate your app gradually as a hybrid application. You don't have to do it all at once up front.
- timetraveller26 5y agoDevelopers can also migrate to Vue