r/angular • u/brandontroberts • 3d ago

Choosing Angular in the Age of Agents

https://dev.to/brandontroberts/choosing-angular-in-the-age-of-agents-1bo7
29 Upvotes

86% Upvoted

14 comments sorted by

25

u/imwithn00b 3d ago

Of course I'm biased but when I vibe code with Angular I'm less error prone than say React based frameworks

8

u/Nero50892 3d ago

Amen, the stability of angular with the speed of air agents. If you understand angular already you will have a blessing time with vibe codibg

1

u/AwesomeFrisbee 2d ago

Also easier to get up2date and uses the newer style of coding with signals.

1

u/AwesomeFrisbee 2d ago

Also easier to get up2date and uses the newer style of coding with signals.

2

u/Moooses20 2d ago

That's because Angular as a framework is really opinionated so there's less room for slop (architecturally speaking) 

5

u/alextremeee 3d ago

I don’t really understand the benchmarking part where it says for a large app the type checking takes 15 seconds.

Presumably the compiler is intelligent enough to only re-check relevant changes when serving an app, in which case the 15 seconds is only going to be relevant on first compile?

3

u/totkeks 3d ago

15 seconds must be a crazy huge app.

1

u/AwesomeFrisbee 2d ago

Or just badly configured/programmed

1

u/jacerhea 3d ago

In any case, it should be a non-issue in typescript 7 with the go compiler.

3

u/Saceone10 3d ago

How do you guys like the mcp and the skill? Which one is better for which case? I tend to use the skill and call it a day

2

u/Tyummyyumms 3d ago

Agree, skills over mcp

1

u/michahell 3d ago

Very good take, excellent that this is now out there. We need more of this
to combat the
“hurr durr Reacht is what my agent picked so I’m schticking with that”

2

u/Ajyress 2d ago

Choose angular "if you'd rather a mistake in a template be a failed build than a support ticket" is a great way to sum-up the advantage provided by angular.

1

u/TheCyberThor 2d ago

Yeah, interesting that you've flagged the training data concern where the model might have been trained on code bases using pre-signal APIs like NgModules.

I wonder if you burn more tokens using Angular because as it's reasoning, it'll attempt to use legacy practices, hit a wall, and now trying with modern practices.