Mark Thompson, a Google senior developer relations engineer, shares what's new and what's next for Angular.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

Angular has made significant strides to become more developer-friendly and performant. Key improvements include a simpler syntax for templates, the introduction of Angular Signals for better reactivity control, and enhanced lazy loading at the template level. Upcoming features like partial hydration are set to further improve performance, while AI integrations offer new possibilities for app development.

Angular’s Efforts To Be Easier and Developer Friendly

With standalone modules, @if notation and many other improvments, i feel like angular is great for large applications.

When I was starting front end, I’ve chosen Angular (because I already knew <a href="http://ASP.NET" target="_blank" rel="noopener nofollow">ASP.NET</a> and the people said Angular is more commonly used with angular) and I found it hard to understand when I tried React it was a completely different experience, it’s good to know that Angular is trying to be more developer friendly like react/next do.

NgModules made me look for something else, then I moved to Vue2. Nowadays It’s React 👌

I’ve been working with Angular since 2018, and before that with angular.js. I never liked React because of JSX. I love the concepts of Vue which is supposed to have taken the best of both worlds, but alas, (a) it doesn’t pay the bills, and (b) when I tried to create a simple project, I could not figure out how to go about it past a certain point.
All this being said, this article does a terrible job at explaining where Angular is headed (signals, computed and effects are not “components”). Wherever Angular is headed may bring in some new dev blood but is unfortunately going to turn a lot of us “old” Angular developers away from it. The Angular team is focusing too much on SSR (the article mentions hydration but neglects to mention the obvious implication of SSR), and they seem to not care about what I think is the vast majority of Angular usage in the corporate world (where I work), which will never use JS on the server (even to do just SSR). So, unless I’m missing something, Angular is headed in the wrong direction and we might as well start looking into other frameworks.