14 ms·
I imagine they got tied up in all the .Net changes between 2016 and now. I wouldn't be surprised if they were just waiting for Microsoft to pick a path long eno
by da_chicken 5y ago
I imagine they got tied up in all the .Net changes between 2016 and now. I wouldn't be surprised if they were just waiting for Microsoft to pick a path long enough to have a target.
.Net 6 of makes sense because it's supposed to be an LTS version. However, if the release and EOL projections[0] I don't think it actually matters all that much: "LTS releases get free support and patches for 3 years. Current releases get free support and patches for 18 months."
That feels fairly aggressive for a library and language for business applications. I imagine many projects won't be released until the version of .Net used to build it is EOL.
[0]: https://dotnet.microsoft.com/platform/support/policy/dotnet-core https://dotnet.microsoft.com/platform/support/policy/dotnet-...