31–40 of 54 posts
I 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.
Totally 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.
> 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.
Earlier quoted context omitted.
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?
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.
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!
I used the 10-step process outlined here and it was pretty straightforward: 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.
Totally 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.
I also think it's worth pointing out that people have very different understandings of what "very big projects" are. I think you mean projects with many different people working on it, in which case I agree, but often people misinterpret these statements thinking that their 1-5 person team working on a web app is a "very big project" because they have a million users.
Totally 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.
> 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.
As 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.
I 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.
I 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.
I 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.
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.
Earlier quoted context omitted.
I 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.
Modern 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 Spri…
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.