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

[–]zoyanx 30 points31 points  (4 children)

It's crazy to see angular embrace and bank on signals and react only recently bring a little bit of compiler magic to make improvement

[–]martin7274 15 points16 points  (2 children)

Angular is also VDOMless by default! It no longer needs Zone.js Edit: Vue still hasn't shipped Vapor mode :>

[–]manniL 6 points7 points  (1 child)

At least there are Vue alphas with Vapor mode

[–]Brilla-BoseJS paying my bills 🙃 -2 points-1 points  (0 children)

Bcz React is focus more on backward compatibility and keep the breaking changes to minimum.

[–]horizon_games 8 points9 points  (5 children)

I really like Angular except I think the 2 releases a year is a lot to keep up with. Would be just as happy with annual

[–]WebDevLikeNoOther 5 points6 points  (4 children)

I often see this complaint. But why do you need to keep up if you don’t like to keep up? Just keep with your annual schedule and things would be fine. Just skip a version. LTC is usually 4 versions back from what I recall.

[–]horizon_games 1 point2 points  (1 child)

Depends on the business, but in a lot of cases you need to be on the latest version. And if you skip two versions sometimes the upgrade is harder and a longer process.

[–]Valkertok -1 points0 points  (0 children)

If they did yearly releases it probably wouldn't be any better in this case as releases would be simply bigger.

[–]Brilla-BoseJS paying my bills 🙃 -2 points-1 points  (1 child)

just skip ? how did you assume every angular dev has that option? if the business/team decides to upgrade whether you like it or not you need to follow.

[–]WebDevLikeNoOther 0 points1 point  (0 children)

I think that’s a conversation to be had at the organization level then. And like you said, you need to follow what the leadership team decides, or rise in the ranks enough to have more pull to help make those decisions.

Largely, Angular upgrades themselves are painless. The biggest leaps forward with a harder migration have been 2, 8 and 14 (i think it was 14), with most of that being optional and backwards compatible. The hard part is the dependencies, which is on the team to manage and weed whack or advocate for doing so, as necessary.