Earlier quoted context omitted.
I’ve never said that .Net wasn’t great. I said it would be dumb to tie your career to .Net Framework that is Windows only and is maintenance mode instead of .Net Core. I’ve had enough conversations with you on HN that I know you know the difference. And I’ve said that most of the energy is going toward mobile, the web and services. No one outside of game makers are making money selling mobile apps. But they are makin…
.NET Framework and .NET Core are .NET. Windows is doing pretty well across 80% of desktop, laptop and 2-1 hybrid devices. As mentioned, I spent the last 5 years doing Forms/WPF/UWP, and there is plenty of work there. Just as there is for anyone wanting to bother with either Qt or macOS. At least in Europe no one starves by focusing on being a desktop developer.
As mentioned, I spent the last 5 years doing Forms/WPF/UWP, and there is plenty of work there.
There were also jobs for Windows CE developers in 2015 after MS abandoned it in 2007, would that have been a good career move?
Microsoft said that they are only focusing on compatibility with Windows for .Net framework going forward and they will be adding features to .Net Core that won’t be ported to .Net Framework.
https://www.itwriting.com/blog/11291-state-of-microsoft-net-...
This is now changing. Microsoft has shifted its position so that .NET Framework is in near-maintenance mode and that new features come only to .NET Core. Last month, Microsoft’s Damian Edwards stated that ASP.NET Core will only run on .NET Core starting from 3.0, the next major version.
From the C# program manager.
Async streams, indexers and ranges all rely on new framework types that will be part of .NET Standard 2.1. As Immo describes in his post Announcing .NET Standard 2.1, .NET Core 3.0 as well as Xamarin, Unity and Mono will all implement .NET Standard 2.1, but .NET Framework 4.8 will not. This means that the types required to use these features won’t be available when you target C# 8.0 to .NET Framework 4.8.