Hacker News new | ask | show | jobs
by gregmac 211 days ago
> if your source code is based on newer .NET you have to update to a new version each year

.NET has a really refreshingly sane release life cycle, similar to nodejs:

- There's a new major release every year (in November)

- Even numbers are LTS releases, and get 3 years of support/patches

- Odd numbers get 18 months of support/patches

This means if you target LTS, you have 2 years of support before the next LTS, and a full year overlap where both are supported. If you upgrade every release, you have at least 6 months of overlap

There's very few breaking changes between releases anyway, and it's often in infrastructure stuff (config, startup, project structure) as opposed to actual application code.

2 comments

Ah, but if you use node.js you get breaking changes every other day from dependencies on dependencies you didn’t even know you had.
The in the box libraries for .Net (even if via Nuget) are much more stable by comparison.
> Odd numbers get 18 months of support/patches

The recently fixed the friction with odd number releases by providing 24 months of support.