3 ms·

I think there are some developers who would consider .NET 5 a huge breaking change. .NET (Framework) 4.8 looks like the predecessor but has features (rightfully

by oaiey 8y ago

I think there are some developers who would consider .NET 5 a huge breaking change. .NET (Framework) 4.8 looks like the predecessor but has features (rightfully) not available in .NET 5. I like the vision but hate the name. .NET Core 4.0 would have done it. When you market software engineers stick with patterns. This looks like a lot of managers have feedback to stuff they did not understand in the first place.

cspierre 8y ago
I love the name. The numerous .Net monikers are confusing. Framework, Core, Mono... each with overlapping support for various frameworks and platforms. I expect new .Net developers to be overwhelmed trying to figure out the differences, as I was. The monikers were misleading. This feels clean, looking forward to it. Does "Core" mean core functionality? Then what is ".Net Standard"? Is .Net Core cross platform or Mono? Why can't I use .Net Core library with Xamarin? Is Xamarin .Net Mono? Should I use .Net Core Winforms or .Net Mono?