cspierre

I mean that the Mono project has already ported WinForms to macOS and linux.

Looks fine to me! https://github.com/dotnet/winforms/pulse

I don't know much about WPF, but it seems to be in an odd place with UWP. The fact there are no plans to port WPF MacOS/Linux, combined with the increasing emphasis on cross-platform... I'm curious where it goes from here.

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?

My guess is we aren't so lucky just yet. UWP has so much Windows 10 device specific functionality, and I think that Xamarin.Forms already satisfies this need.

Instead, what I see them doing is making it easy to share code between UWP and other platforms. There are so many competing options for code re-use, hopefully .NET 5 can consolidate things a bit without sunsetting Mono projects

No Lies! Mono already supports cross platform winForms, and recently the ability to embed Xamarin.Forms views in both mobile and desktop.