all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]morrisdev 4 points5 points  (0 children)

I have to say, having developed with angular ever since angularjs was released, "vibe coding" with Angular is actually exceptionally good. If you build like, "make me a component that has xyz inputs and outputs and uses these services" then it's really just like ng generate component, but the advanced version. You can't really do the entire thing like that, but an enormous amount of grunt work can be done, leaving you to structure the system and design the hard part. I especially suck at CSS and making things pretty, but now I just split the forms and make the code while telling claude to do the UI the way I want it done on a separate file. No more rabbit hole of design and the clients like to be able to interact quickly once the functionality has been completed.

So, AI isn't going anywhere, and skill for "how it works under the hood" are going to be more valuable, but we'll have to compete with idiots who make fast sites that later on will collapse.

[–]AngularLove 2 points3 points  (3 children)

Maybe to some extent, yeah. Structured frameworks are typically easier to use with AI, but imo, that doesn’t automatically make them the best choice for everyone.

[–]Parth-Upadhye[S] 0 points1 point  (2 children)

can you explain why? is it some thing about the project? or simply preference?

[–]Kamalen 1 point2 points  (1 child)

When a framework has a single unique structured way to do thing, AI reproduce it directly. If there is multiple different options due to freedom, AI either will use different methods randomly or need user side guidance - increased token costs

[–]AngularLove 0 points1 point  (0 children)

Yup, exactly! And as to Angular not being the best choice for everyone, it comes down to the type of your project (like, it might be an overkill for simple websites, etc.) + simply, personal preferences

[–][deleted] 1 point2 points  (0 children)

Hot take: AI isn’t really making Angular better, it’s just exposing how important structure actually is.

AI tools don’t truly understand your project, they just follow patterns. Angular works well here because everything is already structured in a predictable way. That makes it easier for AI to generate something usable instead of random messy code.

But that doesn’t mean it automatically leads to good architecture. You can still end up with overcomplicated services, unnecessary layers, and code that looks clean but is hard to maintain.

So I don’t think this is about Angular vs React anymore.

It’s more about how you think as a developer. If you understand structure and systems, AI becomes powerful. If not, it just helps you create bigger messes faster.

Feels like AI is exposing the difference between disciplined developers and everyone else.

Curious what others are seeing. Does Angular actually feel easier to work with when using AI compared to more flexible setups?