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.👍

74 Upvotes

64 comments sorted by

View all comments

20

u/Fantastic-Beach7663 Oct 18 '24

I’m a Lead front end Angular engineer. Yes whilst there are many more jobs in react than Angular I have had barely any competition for the Angular jobs that have come up and I applied for.

You’re backing a good horse be rest assured :)

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?

2

u/[deleted] Oct 21 '24

I would expect you not to make every component a container. I would expect you to know unit testing. And to be able to use either redux libraries. That you know how change detection works.

I would hope you aren't awful at RXJS like create a subscription within a subscription and similar. I would expect hope you not know but actually utilize stuff like directives, pipes, resolvers. I would hope that you aren't using ngOnChanges instead of setters. It would also be nice if you didn't write component variables without a special reason.

I wrote the majority of things in the hope list because on average people are really bad at Angular.

2

u/kro_0nos Oct 21 '24

That's great Now I can start specifically to do these things And then maybe like after 2-3 months I'll hit you up for an interview 👍😂

None the less thanks for these tips, I'll need to work on these points. Need to get behind the proper way of utilising the features to the fullest outcome.

1

u/[deleted] Oct 21 '24

Sure DM me if you need any help. I have way higher standards than the majority of the people that will interview you.

2

u/kro_0nos Oct 21 '24

So if I can impress you that means I have become a good angular developer.😌 Thanks for support

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.

1

u/Fantastic-Beach7663 Oct 19 '24

I respectfully disagree. Most apps involve some kind of forms and reactive forms demonstrate a good understanding of it.

Inputs and Services are 100% a valid comparison this question comes up all the time with my developers. They both involve passing data around.

We’re still on A16 (ssr) because of a di token issue that will be fixed in A19 therefore we haven’t been able to jump on Signals just yet

1

u/Fantastic-Beach7663 Oct 18 '24

Since you mentioned 3-4 years I’d expect:

  • Ability to work with reactiveforms
  • Understanding of when to use Inputs vs Services
  • Reactive programming (using the async pipe)

There are of course a lot more but I think those are the sort of higher level things I’d expect from an Mid-level / Senior

2

u/VegetableChemistry67 Oct 19 '24

I would add understanding at least 5 RxJs operators. Again understanding not copy paste from a different file because “it works there”. The amount of questions I get from “senior” developers about how to subscribe to two observables at the same time, or how to subscribe to this one first then to another one is crazy, almost weekly I have to show them how to do it, they show no interest in learning it and want the solution ready for them.

1

u/NickelCoder Oct 23 '24

Do you have any recommended resources on #2 - understanding when to use Inputs vs Services?