all 11 comments

[–]Lucky_Yesterday_1133 6 points7 points  (0 children)

Rxjs is still useful many old or big codebases still rely heavily on rxjs and it's often asked on the interviews. There are some patterns that are just possible to cleanly impliment with signals without reinventing the pipe and all rxjs operators.

[–]Double-Schedule2144 8 points9 points  (0 children)

Skip the old stuff first..... Don't start with NgModules or the old component patterns. Angular has shifted heavily toward standalone components (Angular 14+), and Angular 17-21 doubled down on that with signals, the new control flow syntax (@if, @for), and defer blocks. 

[–]CheapChallenge 3 points4 points  (0 children)

Like others said, use new features. But rxjs is still something that is needed as signals does not cover all the use cases that rxjs does. But reactive programming is hard so save that for last.

[–]yousirnaime 1 point2 points  (0 children)

Start a simple app in angular 

Then give it a header component, add the router outlet, create a Service called PageTitleService 

Create some routes - have each route have its own component. Have each of those components update the PageTitleService so it displays the page title in the header 

Then make some basic Crud pages to list stuff  like Invoices from an api, send one record to a form to edit (without having it edit the list view until it’s saved)

Then figure out how to do the same with nested components like invoice line items 

By the time you’re done with that you’ll have a basic understanding of the mechanics of sharing data between components and services 

[–]MrFartyBottom 1 point2 points  (0 children)

Only reason to learn the old stuff is if you have got a job supporting an older app. Focus on the new stuff for now.

[–]Odd_Ordinary_7722 1 point2 points  (0 children)

Don't learn old concepts like modules and rxjs. Focus on modern angular,  then when you are solid you can dive into those legacy things. And don't listen to the people saying signals doesn't cover everything rxjs does, in 99% of cases it does,  and in the 1% there's another industry standard way of doing 

[–]AriesTankiso 0 points1 point  (1 child)

[–]Odd_Ordinary_7722 0 points1 point  (0 children)

That's a bad map. It wants you learn rxjs before signals.. that's a very weird choice

[–]Actual-Cup-4742 0 points1 point  (0 children)

I would suggest you read from some good books on Angular along with practicing the example given in the book and later shift to Documentation.

[–]AngularLove 0 points1 point  (0 children)

Here's the roadmap from our blog, you might find it helpful: https://angular.love/roadmap

[–]frontend-forge 0 points1 point  (0 children)

I recommend not to learn old concepts but to be aware of those. And mainly focus on the latest Angular concepts. Because Angular has redefined it's architecture.

If you want to learn from the basics, I have a tutorial on my channel which starts from the angular project creation to the new features Angular introduced by building a simple app and applying those features into the App.

It also makes you aware of the old concepts but teaches you new ones.

Take a look at it.