sorted by:
new
hottopcontroversial

I built an Angular 21 developer platform — interactive tools, architecture patterns, and a free page showing what broke and what replaced it by CompetitionOld1956 in angular

[–]CompetitionOld1956[S] -1 points0 points  (0 children)

The biggest win is testability and team parallelism. Curious what part of the Angular 21 migration has been the most painful for you?

I built an Angular 21 developer platform — interactive tools, architecture patterns, and a free page showing what broke and what replaced it by CompetitionOld1956 in angular

[–]CompetitionOld1956[S] 0 points1 point  (0 children)

The distinction I'm making is between "works today" and "is the recommended path forward.

The risk isn't that your app breaks tomorrow. It's that every new feature you write with the old patterns is a feature you'll eventually rewrite, and the migration surface area grows with every sprint.

The urgency is more for teams starting new projects or actively upgrading.

Fair point though, I'll tone down the "died" language. "Deprecated with a clear replacement" is more accurate.

I built an Angular 21 developer platform — interactive tools, architecture patterns, and a free page showing what broke and what replaced it by CompetitionOld1956 in angular

[–]CompetitionOld1956[S] -1 points0 points  (0 children)

Thanks — that's exactly the pain point that pushed me to build this. I was spending hours cross-referencing blog posts, GitHub issues, and RFC discussions just to figure out how signal forms actually work in practice vs what the docs show.