What about Angular 2+?

After the disaster of AngularJS that we are still paying external EOL support on, I will never trust another Google led framework.

▲

microflash 6 hours ago | parent | prev | next [-]

Angular 2+ is equally horrible. Having spent 6 years on various versions of Angular, their migration story time and again has been an incredible pain.

These days I use web components for component writing and frameworks to handle routing, state management, bundling, and so on.

	▲	tcfhgj 11 minutes ago \| parent [-]
		can you compare it to other frameworks? I migrated from Angular 4 to 18 (including ngrx and material) and didn't find it especially problematic. Migrating mostly was little effort and consisted of automatic migration and walking through the provided checklist (mostly to ensure I didn't miss anything important), but I don't have any comparison in the JS SPA ecosystem.

▲

jamesrr39 4 hours ago | parent | prev [-]

I tried Angular 2+ back in the day. I found it frustrating to learn as the API had changed between versions, and when searching for help you would come across a blog post/stackoverflow answer, start implementing it and realise it didn't work in the version of Angular your project was in. Frustrating.

Tried React afterwards, this frustration didn't really exist and it was much easier to pick up.

	▲	pjmlp 4 hours ago \| parent [-]
		The frustation is pretty much there under Vercel's stewardship, especially when React comes in the shape of Next.js. It is apps or pages, which supports what, what new use cases is "use..." now for, ....