Member-only story
Is Angular Better Off Without Change Detection?
Know why Angular should get rid of its change detection strategy
Like most developers who began on C# and .NET, I eventually needed to write a responsive frontend to interact with the APIs that I was creating.
At the time, Angular seemed like the obvious choice. It’s written in Typescript, which was created by Microsoft (and has some similarities with C#). Because Angular is strongly opinionated on how my app should be laid out, it made it comparatively easy to get started.
At the time when I was choosing, the two big players in this space were Angular and React. I thought of the type-safety that Angular gave me as a plus, and I also felt that React’s JSX templating was not an intuitive experience. I also found it easier to update the data in my components, by using view bindings in Angular, than it was to use React and the setState() method. Ironically, after using Angular for a couple of years, it turns out this comparative “ease” to update views also contributes significantly to what I think is the biggest downside of Angular.
Over the years, I’ve created quite a few Angular apps, including one I created recently for a customer (that interacts with a .NET API). And I can safely say, that I was wrong about Angular. Why though?
