Angular is still developed. Last years performance improvements (Ivy engine) causes build time to be fast and comparable to React. Also interactiveness is comparable to React.
Angular enters 2022 year as a strong framework that proves its value for people who like to focus on design and user experience rather than handling technical issues introduced by complicated sets of libraries that form frameworks around React.
While React development is also ongoing and enables developers to hotwire amazing projects, Angular holds to the mission of being stable, predictable framework that you can learn once and transfer the knowledge to every project.
Year 2022 is for Angular deciding. Vue - a in between tries to buy programmers keyboards. Svelte is another library around. But the real competitor for Angular is Ember. The only framework that provides similar level of coding comfort.
Eventually 2022 will be a year of serious decisions. Will Angular be removed to replace or with intensively marketed React? Will developers working earlier with jQuery or React, Vue, Svelte put their horses on well thought through framework that helps to focus on user experience?
Will developers support Angular by adjusting libraries accordingly? Aside from technical discussions, and decisions, 2022 fate depends more on trends, just like fashion is dependant.
One is sure, Angular is here to stay supporting developers and users in in proving and having state of art experience.
Latest comments (14)
Important resources related to angular
bio.link/angulardev
It's dead. It's on Killed By Google
Your comment puzzled me for a second. Than I recalled that Google announced that Angular.js will be phased out. Ok.
Angular.js aka Angular 1 is an old version of Angular. And true, it is phased out.
However, the "real" Angular everyone is using is Angular CLI aka Angular 2+. It is actively developed and is here to stay.
Can't blame. Angular naming was ambigous
There is use for Angular and use for React.
In my opinion, React for small-medium projects. Rest - Angular.
I know what you have in mind. However I wonder if I'd choose React for my small medium projects.. Because setting up and wiring React setup is much more time consuming than Angular. Maintaining all libraries around React as well. Taught call
I am not sure from where this idea 'React for small or medium project' has originated, but React is use to build Facebook.com, which in no means a small or medium web application. I have work on both React and Angular, and as a new JS developer I feel React is faster to setup and start working on compared to Angular.
It is really not clear what Facebook uses for the frontend. Maybe somewhere there is React, but it does not seem to be nowhere near React we all use. It is just different scale of a project.
What makes setting up Angular harder for you than React?
Here is an article from FB engineering team
engineering.fb.com/2020/05/08/web/...
and an excerpt from the same
Today, we’re sharing the lessons we’ve learned while rearchitecting Facebook.com, using React (a declarative JavaScript library for building user interfaces) and Relay (a GraphQL client for React).and I am not saying Angular is not relevant, it's relevant and much needed framework. I am just commenting on the fact that React is also for large project, and not only FB but tons of other companies (including mine) uses it.
It is a great starting point for you to learn more about Facebook stack.
What makes it harder for you to set up Angular project compared to React?
Learning Typescript, using angular specific way of doing things. As a new JS developer I just want to add script tag including any JS library that I want to use and start writing code.
The fact Facebook and more organizations use React over Angular in big projects doesn't really prove something. I work in big company, and one of the product I'm working on is implemented in React.
As this product founded, the reason for picking React wasn't really serious in aspects of scale. They just chose.
Sometimes, project's environment is being chosen just because the "founders" are in rush, or they just know React so they say "No time to learn the Angular framework now. We know React - let's go"
I would use Angular for high-scales project and ones that may grow because Angular supports out of the box the IoC concept.
Also you get the dependency injection (services) option over Redux - which I prefer.
Thanks for sharing. It lines up with the thing that React is jQuery+. Nothing wrong about it, among other for reasons you wrote. The thing is that Typescript and some other standards are already set up in Angular. While to reach the same level of framework setup with React takes a lot more time and effort. Also, not always worth it. For example Typescript's negative perception comes directly from React's and Redux failure to recognize OOP. They make people hate TS
Ok, good for you.