4 ms·
.NET Core wasn't exactly built for cross-platform, that seems to be a (very welcome) side effect. The big deals for .NET Core (versus .NET Framework) is that it
by WorldMaker 11y ago
.NET Core wasn't exactly built for cross-platform, that seems to be a (very welcome) side effect. The big deals for .NET Core (versus .NET Framework) is that it is: A) Open Source (yay!), and B) Componentized (.NET Framework is a giant monolith that roughly followed Windows versions; .NET Core is a set of libraries that each can independently iterate with semver).
The new componentized nature of .NET Core (and the other *Core projects here) is really the big deal here, even without the added benefit that it is Open Source and cross-platform. The benefit for developers to switch to .NET Core (or to support both for the time being) is that you are a lot less reliant on/restricted by the version of Windows your users or servers are running. With .NET Core now things like even the System namespaces are now available as semver-versioned NuGet packages that you can upgrade as a developer, rather than wait for your users to upgrade their Windows version (or install a massive .NET Framework upgrade), or your corporate server to upgrade its Windows Server or .NET Framework. This is especially great for ASP.Net developers as it makes it easier to run servers and easier for your applications to run on whatever servers you have available. It's useful to application developers because .NET Core very much is the .NET supported by the Windows 10 "Universal Windows App" platform, and things like .NET Native are made possible thanks to the componentization efforts of .NET Core.