3 ms·
Oh, thank you for that. I’m really happy to hear there’s been movement on this front. Hopefully Unity will get there eventually - I suspect their own solutions
by t8sr 5y ago
Oh, thank you for that. I’m really happy to hear there’s been movement on this front. Hopefully Unity will get there eventually - I suspect their own solutions to some of these problems might be holding back adoption of more recent .Net versions, at this point.
- runevault 5y agoThey claim an upcoming project is to upgrade to .NET 5 (though at this rate I would more expect 6).
- novaleaf 5y agoyes, just as you imply, don't hold your breath ;)
- da_chicken 5y agoI 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-...