I am using asp.net core 2.1 for .net framework because it comes handy to load third party .net framework dlls inprocess. I do not have any power to convince third parties to move to .net core.
Yes.
It's not a secret. Microsoft has said that .Net Framework is basically in maintenance mode and "will move slower". They are moving EF6, Winforms, and WPF to .Net Core (Windows only).
https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on...
I've been developing on top of Microsoft environments for over 20 years and .Net is by far my favorite language. But, the writing is on the wall. Anyone who wants a long term career in development needs to run away from Windows as fast as possible and slowly move away from focusing exclusively on .Net.
Linux even dominates on Azure.
https://www.zdnet.com/article/linux-now-dominates-azure/
Microsoft knows that Windows can't compete in the cloud and selling Windows for desktops is not the future.
From my point of view the grass is still greener in this side.
he's saying windows as a programming platform is dead. You can keep .Net and Java, its just going to be .Net core and Java, and its going to run on linux machines.
Its a matter of time until Visual Studio runs on linux, but that's the direction they're heading. Visual Studio Code already does
Not exactly. I'm saying that Windows as a deployment platform is dead. You can keep developing on Windows and deploy to Linux. I do it all of the time.
But I agree that frameworks which can ONLY deploy to Windows (.Net Framework) will die in favor of those that are cross platform (.Net Core).
Linux won a long time ago and is so far ahead in tooling and ecosystem support that it just isn't worth it to compete in the server OS space. And that's better for everyone since we can consolidate effort and products.
Like every monoculture things either stagnate, or we start getting features just to work around botherom instead of actual innovation.
I tremble to imagine how many cores and GBs would be needed to have VSCode with the same capabilities of Visual Studio Ultimate, while running at comparable performance.
Specially when comparing with the likes of Sublime, which I gladly payed for.
Wouldn't that encourage a switch to a totally new system? If you have to do a ton of ground-up work to get VS working 64 bit, you could argue you as well expend the same effort in getting VS Code to a level where it can be used instead of VS.
https://blogs.msdn.microsoft.com/ricom/2015/12/29/revisiting...
What's worse is that VS doesn't even follow its own recommendations. Even with the massive upgrades over the past year, it's still extremely slow and laggy on any sizable solution.
In process plugins look cool, but they just bring everything down when they misbehave, plus it is another opportunity for exploits.
Peformance can be improved by actually writing the plugins in languages that compile to native code and eventually use shared memory.
Now if one uses node for everything naturally it doesn't scale.
https://visualstudio.microsoft.com/vs/mac/
And there is always JetBrains Rider for Linux
Windows -> Linux: Using Windows on the server is a dead end. Every time I have to use anything Windows based, especially in the cloud, it's a double hit -- the same compute resources cost more because of licensing and you need more resources to run Windows. I can't imagine why anyone starting a project today would tie themselves to Windows. Even if you like Windows and .Net as a development platform (I do), it makes no sense to deploy to Windows if you don't have to.
.Net Core -> Javascript Everywhere. I hate the trend as much as anyone, but, I don't see .Net Core getting much adoption for greenfield projects unless their developers are already .Net users. Even the more career driven .Net developers are moving toward Node for resume reasons.
Out of the two, it's career suicide to focus solely on Windows. .Net Core has a longer shelf life and you can remain marketable if you know .Net (Core/Framework) + Windows and Linux
Also the cloud is still a foreign word to many companies.
Finally, every time I have to touch Node eco-system it saddens me, npm gets several thousand modules for a plain Hello World and lets not pretend V8 is the same performance ballpark as using a strongly typed language that can be AOT/JIT to native code, with real multi-core support.
I'm also not arguing that every company will eventually go to the cloud or that every company will move toward Node. But, staying in the MS ecosystem will also lead to career stagnation. I'm nowhere near the west coast and I'm mostly your bog standard "Enterprise Developer/Architect". But the minute I put "AWS","Linux","Node" on my LinkedIn profile, the more serious discussions I had with consulting companies (not recruiters) with offers of $20K-$30K more than companies were offering "Windows Enterprise Developers"
Plus as you notice from my comments I do polyglot development, and luckily there are other options than spending 8h with Node every day.
Also building up soft skills and domain knowledge is another way to keep relevant, while staying on the same stack.
I know that I was completely uninterested in learning it while it was a Microsoft proprietary project. But that was always a shame because from a language perspective, it's exquisitely designed. Now that's free'd up, I expect a lot more adoption.
Node is great, but it's actually pretty slow. And it doesn't have anything to compete with Rails/Laravel/Django/ASP.NET MVC which are still super-productive.
- Yours, a Frontend/Node/Python/PHP Dev.
This has more to do with per hour billing. Over the long term no company wants to pay 2x for the same compute resources that they don't need to maintain.
For the on-premise enterprise you will continue to see sizable market share with Windows Server for the foreseeable future, since those companies already have Windows-trained sysadmins to manage them (along with their huge inventory of Windows corporate desktops).
But I’m not a “Linux guy” yet. I’m trying to move up to being an overpriced “consultant” that tells companies how they can save money via automation, using best Devops practices, etc. and why they don’t need as many infrastructure people.
I’m a software architect who plays the role of an AWS Architect when necessary.
The Azure guys will happily tell you that they believe the best way to automate and run Linux servers is as VMs and containers on Windows Servers.
Isn't .NET the runtime/environment and C# the language?
What about webforms? I haven't been able to find any info on that one.
Presumably, as Teams gets closer to eating S4B it will catch up on more of the rest.
* Server-side WCF endpoints. We're currently exposing WCF endpoints, which we must maintain for our current users.
.NET Framework 4.8 will be the last release though. Innovation will happen in .NET Core and the packs available for it (e.g. the Windows Desktop Pack).
Source: I'm working on the Mono BCL+Tools team at Xamarin/Microsoft.
Unfortunately, yes. I would've liked to have seen support for netstandard rather than a particular runtime, I worried that it means people will get sloppy and just target whatever their web framework is targeting.
You've luckily got three plus years of support, so hopefully in that time you'll be able to make a plan about 3rd party dependencies.