Why I Chose Angular in 2024 (and Still Use It)

Every developer has an opinion on frontend frameworks. Mine is simple: Angular is underrated, and React gets too much of the spotlight.

Let me explain.

---

The Ecosystem Problem

When you pick React, you're picking a UI library — not a framework. You still need to choose:

• A router (React Router? TanStack Router?)
• A state management solution (Redux? Zustand? Jotai? Context?)
• A form library (React Hook Form? Formik?)
• A data fetching strategy (SWR? React Query? plain fetch?)

That flexibility is great for small projects or teams with strong opinions. But for enterprise applications — especially in FinTech — you want consistency.

---

What Angular Gets Right

1. Everything is in the box

Angular ships with:

• A router
• An HTTP client
• Dependency injection
• Reactive forms
• A CLI that actually works
• A testing framework

You can focus on building your product instead of fighting over tooling.

2. TypeScript is a first-class citizen

Angular was built for TypeScript. The integration is seamless — decorators, interfaces, strict mode — it all just works.

3. Signals (Angular 17+)

With the introduction of Signals, Angular now has a reactive primitive that's simple, predictable, and performant. It's made state management a joy.

import { signal, computed } from '@angular/core';

const count = signal(0);
const doubled = computed(() => count() * 2);

// Update
count.set(5);
console.log(doubled()); // 10

4. Standalone Components

Angular's move to standalone components has made the framework feel much lighter. No more NgModule boilerplate — just import what you need.

---

When React Makes More Sense

I'm not anti-React. For:

• Small, simple SPAs
• Teams that already know React deeply
• Projects where the ecosystem flexibility is an asset

React is a great choice. It's just not always the best choice.

---

The Bottom Line

I use Angular professionally because it scales well, keeps teams aligned, and has everything I need built in. I use it on side projects because I know it well and can move fast.

The best framework is the one your team understands and can maintain long-term. For me, that's Angular.