.NET Core is the open source, cross-platform, and fast-moving version of .NET. Because of its side-by-side nature it can take changes that we can’t risk applying back to .NET Framework. This means that .NET Core will get new APIs and language features over time that .NET Framework cannot. At Build we showed a demo how the file APIs are faster on .NET Core. If we put those same changes into .NET Framework we could break existing applications, and we don’t want to do that.
.NET Standard, .NET Core, and .NET Framework...I wish Microsoft would be a little less confusing. I wish I had a better idea of where Microsoft is actually going in general, let alone with .Net...It is getting tiring wrestling with the beast.
Has anyone used it here ?
Do you mean Standard, what the announcement was about, or Core, what your quote is about?
I do understand the relationships in .NET, I just find Microsoft docs can be a little...spaghetti. I'm dyslexic, that adds another level of complexity.
I've spent a little too long with my head down in desktop C#/.net framework and I'm trying to workout where things are going. Currently looking whether to invest some quality time into C++/WinRT for Universal Windows Platform. (I think I would like to move away from .NET)
I've only had a quick 'look' at .NET Core while looking at ASP.net so no real use in anger.
...but then Windows Runtime (WinRT) APIs is designed to provide you with first-class access to the modern Windows API (not Win32). I have also seen Microsoft docs that seem to talk about UWP as if it is the new 'Windows' but also that it is a spec for what is available on the different Windows 10 platforms...
All I know for sure is I preferably want to move away from .NET and I'm not interested in web programming.