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 making money selling services that users interact with over the web and mobile - not the desktop.
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.
Again, I know you know this stuff - you were involved in the discussion when it was posted here.
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.
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.
.NET Core is yet to be embraced by most enterprises, everyone is waiting for .NET 5 to actually make the switch. Too much software is now making the transition into .NET Framework 7.x, to bother with half baked support from Core to many APIs like EF6, WCF and components from third party vendors.
From where I am standing, we don't care what Microsoft calls it this month, it is .NET.
It’s not about what you care about the industry is definitely moving further away from Windows desktop apps as it’s main focus and is definitely moving toward services and mobile. How much clearer can you get than the CEO of MS saying they are distancing themselves from Windows as a priority? If enterprises are embracing Linux even on Azure, their definitely not using .Net Framework.
Today more Linux VMs are being hosted by Azure than Windows. Microsoft is making serious investments in cross platform development and making Linux a first class development environment on Windows with improvements in WSL.
EF6 and WCF is legacy. Really? Are we arguing about SOAP in 2019?
It’s not about what Microsoft is “calling it”. It’s about where all of the future emphasis of .Net improvements are.
So REST instead of SOAP is a “coffee shop trend”? That migration has been going on for at least a decade.
We already know the “trend” that .Net is going in from no less than the program manager of .Net. That “trend” is no major new features for .Net Framework and it will be stuck at 4.8.x forever while all of the innovation is happening with .Net Core.
We also know the “trend” of MS’s focus from no less than the CEO of Microsoft - a de-emphasis on Windows and an emphasis on cloud and moving to where the customers are - Linux and services for both web and mobile users.
Don’t you think it’s quite telling that the biggest news for Windows 10 lately is improved support for Linux via WSL 2.0 and how much emphasis is being put on VS Code?
It is, just right now I am working for a customer where SOAP keeps being relevant as ever.
.NET Core will be relevant for this kind of customers in about 5 years time, again we are still targeting 4.7.2 for bleeding edge customers.
Microsoft wants to win the hearts of FOSS developers that buy Macs as pretty UNIX for developing GNU/Linux software and are unhappy with the latest "Pro" offerings without having ever written a single line of Objective-C or Swift, that's all.
It is, just right now I am working for a customer where SOAP keeps being relevant as ever.
This might surprise you, but the world doesn’t revolve around your niche.
NET Core will be relevant for this kind of customers in about 5 years time, again we are still targeting 4.7.2 for bleeding edge customers.
By definition, customers using .Net Framework and SOAP are not bleeding edge. They wouldn’t have been bleeding edge 5 years ago. The industry was already moving toward REST.
Microsoft wants to win the hearts of FOSS developers that buy Macs as pretty UNIX for developing GNU/Linux software and are unhappy with the latest "Pro" offerings without having ever written a single line of Objective-C or Swift, that's all.
Are you really saying that all of Microsoft from the C# Program Manager up to the CEO is wrong for focusing more on mobile, services, and the web than Windows desktop because your niche is still focused on the desktop?
You do realize that most of the world’s only interaction with a “computer” is via the web and mobile don’t you?
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 making money selling services that users interact with over the web and mobile - not the desktop.