News for hackers. Stuff that matters.
Re:Introducing .NET Standard by terrajobst on Monday September 26, 2016 @02:58PM (#12584592)
I can see that being a problem. Let me try to explain:

* We've concrete .NET platforms, such as .NET Framework, .NET Core, and Xamarin. They are the moral equivalent of Linux distributions. * With .NET Standard we now have shared specification that dictates which APIs all these platforms have to implement. That's the moral equivalent of POSIX.

Re:Introducing .NET Standard by crudbug on Monday September 26, 2016 @06:18PM (#12586087)
Yes, this was exactly my point.

The elements are present, just that the way naming is done is very confusing. The different distribution/namespaces should have clear goals without any naming confusions.

Re:Introducing .NET Standard by tobltobs on Monday September 26, 2016 @04:19PM (#12585193)
And where does fit UWP into this picture? Or what should I use if I want to develop apps for Window Store (or whatever the current name is for that).
Re:Introducing .NET Standard by Kipters on Monday September 26, 2016 @06:01PM (#12585980)
UWP is a native framework based on COM. Windows 10 apps use .NET Core (compatible with .NET Standard 1.4) and can access UWP APIs through bindings
Re:Introducing .NET Standard by WorldMaker on Monday September 26, 2016 @04:23PM (#12585224)
The .NET stack in UWP is essentially .NET Core