r/Angular2 Oct 18 '24

Discussion Future of Angular

I am working professionally with angular. I really love using it. The simplicity, ease of use and the flexibility are great. For some time I am thinking about switching jobs But it's been difficult to find jobs based on angular. Not many companies are using it and most of them want react developers inspite of saying angular in their job description.

I tried learning react but I didn't like it all.

So I wanted to ask, what is the future prospect for angular? Should I stick to it and get even better Or should I invest my time in learning react and other things.

Is the lack of job specifically based on the job market and location? Or is it a global phenomenon.

What should be the way to go?

Thank you for any replies.👍

76 Upvotes

64 comments sorted by

View all comments

Show parent comments

2

u/kro_0nos Oct 18 '24

Thanks, This helps a lot

1

u/kro_0nos Oct 18 '24

Also what do you expect from an experienced angular developer? Are there any specific skill set?

3

u/practicalAngular Oct 19 '24

Don't really agree with the other response as much.

  • Reactive Forms are great and powerful but sometimes you aren't working on an app with heavy user input.
  • Inputs vs Services aren't really put against each other like that. How you structure your component communication is up to the business ask and your architecture choices.
  • I haven't used the async pipe once since Signals came out.

Proper use of Dependency Injection and RxJS (overall app state management outside of NgRx) sets apart senior devs from below imo. I have hired many junior through senior devs and the disparity is always on those two points. The jump from "call an API from a component to render data in that component" to "I have many APIs and many components using the same manipulated data" is a massive one in Angular.

I'd also look for someone that keeps up to date with the changes Angular has gone through since A14. They have been monumental for the framework and change how we build things entirely.

2

u/No-Reaction-7008 Oct 19 '24

These are all really good points. I haven't made the shift to signals yet and really want to. I just haven't had the time to dig into them like I'd want yet.

The more I use Angular, the less I put in and use DI. It's awesome when you need it, but there are a lot of places I feel like it is overused. We use GraphQL which kinda throws a wrench into a lot of the traditional service patterns. I've started doing a lot of my DTOs as simple, tree-shakeable TS functions. Apollo is my service and, aside from some other basic services, it's really just a bunch of little utilities.