4 ms·
.Net has the same problem[0] 45% still "regularly use" .Net Framework because, like Java 8, .Net Core broke compatibility and even in spite of Microsoft's effor
by Someone1234 3y ago
.Net has the same problem[0] 45% still "regularly use" .Net Framework because, like Java 8, .Net Core broke compatibility and even in spite of Microsoft's efforts to offer upgrade routes, it is still a hugely painful experience. Particularly for those stuck on libraries like Asp.Net.
Their current best solution is to put a modern version wrapper around .Net Framework and to map between them, but that isn't exactly ideal either (since you wind up with a giant mess).
[0] https://www.jetbrains.com/lp/devecosystem-2023/csharp/ https://www.jetbrains.com/lp/devecosystem-2023/csharp/
- ocdtrekkie 3y agoI actually prefer using .NET Framework for even fresh projects of mine if they are going to run on Windows anyways: Microsoft provides security fixes for new .NET LTS versions for only three years, so your application bitrots rapidly. Meanwhile, .NET Framework 4.8 is several years old and will almost certainly still be getting security updates ten years from today. To be clear, Microsoft provides better support today for Visual Basic 6 than it does many versions of the modern .NET.
- TillE 3y agoModern open-source .NET feels like a totally different community and ecosystem compared to .NET Framework. The Ballmer era focus on Windows, versus Nadella embracing cross-platform software. The old stuff will stick around for basically the same reasons that people still write C/C++ software using Win32.
- steve1977 3y ago> The old stuff will stick around for basically the same reasons that people still write C/C++ software using Win32. Because the resulting applications are much better?
- signaru 3y agoWith my C# codes not heavily tied to specific .Net frameworks, it's not really affected by breaking compatibilities. However I avoid the latest IDE (VS 2022) which come with the latest frameworks as the IDE is often noticeably slower.