You are completely right and not those things are just decorators and and pure classes you can actually drop zone drop rxjs and make it even less. Soon or later they ll face big problems not only write components and functionality and that's it. Once learn how Angular provide solutions they apply for all js libs. I teach thinkers after that if they want react or what workspace will require 3h video will be enough, but principles will remain.
@lukeshiru You can use Promises in Angular, Observables was mainly introduced while support for Promises was still being added in to browsers. As for things like Services, that's a standard feature in many languages and frameworks, it's a standard pattern that is worth learning. React has plenty of its own things that it does that are definitely not pure JS. Just look at JSX which has become so entwined with React that it's often difficult to find any pure React JS code these days in online examples or tutorials.
I've been using Angular for 6+ years (ever since it Angular 2 was in beta) but I've been using JS for a lot longer, so it's not entirely true that developers will always look for the Angular way of doing something. Personally, I've always put any language first, the frameworks and libraries come after. That goes for any language/framework/library combination.
One of the reasons I like Angular is the ability to write large scale applications. The last one I worked on in my previous role was over 40,000 lines of code and contained some very complicated functionality. That scale would have been possible with React, but the effort involved to ensure the code was clean and followed SOLID practices would have been far greater.
Angular isn't overengineered, it's just engineered. It's aimed at application development, and large scale projects. Most often, front end web projects are smaller and simpler, so I can see why it might seem that Angular is _always _the wrong choice. However, what Angular does give is a robust introduction into well-architected code, which is invaluable for front end devs who want to scale their applications into larger systems on the back end. React serves a different purpose, but that doesn't necessarily make it automatically better in all scenarios.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You are completely right and not those things are just decorators and and pure classes you can actually drop zone drop rxjs and make it even less. Soon or later they ll face big problems not only write components and functionality and that's it. Once learn how Angular provide solutions they apply for all js libs. I teach thinkers after that if they want react or what workspace will require 3h video will be enough, but principles will remain.
@lukeshiru You can use Promises in Angular, Observables was mainly introduced while support for Promises was still being added in to browsers. As for things like Services, that's a standard feature in many languages and frameworks, it's a standard pattern that is worth learning. React has plenty of its own things that it does that are definitely not pure JS. Just look at JSX which has become so entwined with React that it's often difficult to find any pure React JS code these days in online examples or tutorials.
I've been using Angular for 6+ years (ever since it Angular 2 was in beta) but I've been using JS for a lot longer, so it's not entirely true that developers will always look for the Angular way of doing something. Personally, I've always put any language first, the frameworks and libraries come after. That goes for any language/framework/library combination.
One of the reasons I like Angular is the ability to write large scale applications. The last one I worked on in my previous role was over 40,000 lines of code and contained some very complicated functionality. That scale would have been possible with React, but the effort involved to ensure the code was clean and followed SOLID practices would have been far greater.
Angular isn't overengineered, it's just engineered. It's aimed at application development, and large scale projects. Most often, front end web projects are smaller and simpler, so I can see why it might seem that Angular is _always _the wrong choice. However, what Angular does give is a robust introduction into well-architected code, which is invaluable for front end devs who want to scale their applications into larger systems on the back end. React serves a different purpose, but that doesn't necessarily make it automatically better in all scenarios.