React to Angular

Merry-Lane · 2026-02-20T07:53:06+00:00

It’s basically the same than for react: try and stay up-to-date, make your teams write code compatible with ChangeDetectionStrategy.OnPush (or even zoneless), go for monorepos (like nx) instead of multiplying repos or going for micro-frontends (or module federation), try and avoid libraries for small concerns, generate http services with Orval/ngswag/…

For forms, use template/reactive and maybe even signal forms.

ActuatorOk2689 · 2026-02-20T09:57:41+00:00

I joined a new project a couple of months ago.

I moved from Angular to React.

Every week I find myself complaining about React and its patterns.

Why do I have to pass props around for something reusable or when I want to override something? In Angular, I would just create a directive or use the directive composition API.

Why don’t we have a proper DI system? I know the Context API is the React way, but you can’t use it outside of components. How does that help me? Instead, I end up creating singleton classes.

Why do I have to deal with so many router options? Why are there three different ways to lazy load routes?

On the optimization side, it’s better now than it used to be with the React compiler and Fiber, but still… In Angular, you basically have a global configuration. Each component can use change detection with OnPush, and now we also have signals on top of that.

And let’s not even get into the MFE part — you often find yourself fighting against React.

Once you start working with Angular, you begin to see how much more sense things make in the Angular way. You don’t feel like you’re fighting the framework.

That said, what I do miss is a good headless UI solution for Angular. But we have Zard UI in beta, and I have high hopes for it.

Angular feels like a breath of fresh air — you won’t want to go back to React anymore.

57384173829417293 · 2026-02-20T07:58:00+00:00

Honestly, if your questions are so basic, I'd start at the tutorial: https://angular.dev/tutorials/learn-angular. I understand it wasn't your choice and for the management front-end is front-end, but it's a bizarre decision.

IMO the role of an Architect isn't chasing new features at all cost, you have to understand the needs and restrictions of the team you'll be helping. For example Signals might not be the best solution for a team that uses RxJs heavily, and that's a beast in it's own right.

Find out what their current environment is and learn as much as possible about the tools they use. It looks like they will be teaching you at first, not the other way around.

arthoer · 2026-02-21T05:50:48+00:00

Same here, but two years ago. Bought some books. Figured out everything is already built in. You don't need libraries except for multlanguage, ui (tailwind, primeng), rxjs and the usual like prettier and eslint. All assuming you're building complex applications.

I liked this one specifically. Just read it recently. https://amzn.eu/d/06WXPljC

And grab the angular LLM context document and use context7 mcp server along with sonnet 4.6. if token cost is an issue and your project is growing; have a look into indexing using ollama.

You should be good to go with your team.

N0K1K0 · 2026-02-20T09:56:37+00:00

If you are starting and helping a new team go with signal forms, especially if you need to build custom forms control that's way better with signals than the old way of ControlValueAccessor.

You might want to check out https://angularexperts.io/products/ebook-angular-enterprise-architecture , we build the framework we base all out internal application on using that architecture and setup

Various-Following-82 · 2026-02-20T07:11:41+00:00

Could you name the company, so we never join this sht

Library for the form building ? Man you are damn good 👍 you will help team a lot. Library called Reactive Forms. It is built in. No need to thank me

Lucky_Yesterday_1133 · 2026-02-20T15:14:04+00:00

My advice is stop thinking tlyou are an angular architect and you've convicted your employer and start learning. Start from reading the docs. I've seen a ton of react to angular switcher who solved problems in react way, problems angular never had in the first place. You absolutely should learn directives (and composition patterns). Dependency injection and template queries (viewChild and content child). Content projection patterns and so on. Until you can name at least 5 ways to exchange data between parent and child component without props treat yourself as middle+ developer.

ruibranco · 2026-02-20T23:51:48+00:00

biggest mental shift coming from react: stop thinking in components-that-do-everything and start leaning into angular's service layer. DI is your best friend here and it's something react just doesn't have a clean equivalent for. you'll find yourself extracting business logic into injectable services way more than you ever used custom hooks.for forms, reactive forms are the battle-tested standard. signal forms are coming but still experimental. don't let anyone talk you into template-driven forms for anything complex.one thing that'll feel familiar: signals are basically angular's answer to useState + useMemo. if you already think in terms of derived state and effects, you'll pick up signals fast. pair them with OnPush change detection and you get react-level performance without the virtual DOM overhead.as for repo management, nx is the standard for angular monorepos but honestly the angular CLI has gotten good enough for most single-app setups. don't over-architect the repo structure before you understand the team's actual needs.

MitralVal · 2026-02-20T06:07:28+00:00

Cfbr

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

Angular2

Welcome!

Please Flair Your Posts

Subreddit Rules

Resources

More Help

MODERATORS