3 ms·
Everytime I start to think Microsoft is heading in the right direction they go and blow it all away again. This week we've already had a new asp.net core which
by SimonPStevens 8y ago
Everytime I start to think Microsoft is heading in the right direction they go and blow it all away again.
This week we've already had a new asp.net core which drops support for .net standard and only supports .net core.
And now, a new version of .net standard that .net fx isn't going to support.
We are right back at the mess of portable class libraries with all their different supported profiles.
It means app devs are constantly dealing with problems like "is this library I want to use, supported by all the targets my app needs to run on", and library devs have a mess of different frameworks and combinations to support, so inevitability drop a few of them unless they are a big project with lots of manpower.
- oaiey 8y agoI need to highlight, that ASP.NET Core never run on .NET Standard. Some parts always have been dual-compiled for netcoreapp2.0 and net46(?).
- SimonPStevens 8y agoAh, my mistake, I didn't know that. Kind of actually enforces my point of the ecosystem being a mess though and the only realistic thing to do is compile for multiple targets.
- WorldMaker 8y agoI believe that ASP.NET Core should be able to move to .NET Standard 2.1 (Span<T> is the big reason they decided they needed to drop .NET Framework support). They dropped .NET Framework, but there's still a case that they can support .NET Standard here, for what that is worth.
- oaiey 8y agoRegards Portable Profile: I think the case is different. .NET Framework will just no longer evolve. It will always stay on .NET Standard 2.0. .NET Standard is not a intersection. It is a small bubble being in a bigger bubble. And the biggest bubble is the latest. The reason Miguel and the Unity folks are so important in this process, is the fact that they have to agree to participate in the latest and biggest version of the Standard.
- titanix2 8y agoExactly. The fact that the .net framework will not implement .net standard mean the latter lost immediately most of its raison d'être.