Earlier quoted context omitted.
> Nowadays it sounds like .NET Core + third-party GUI libraries is the way to go. For reference for those unfamiliar with the terms: .NET Core was the name given to the cross-platform fork of the .NET runtime. It was forked out of .NET 4.x and dropped support for a lot of things in the first versions. It ran on various distributions of Linux and MacOS. At the same time there were forks of other libraries/frameworks i…
Minor nit: from what I understand dot net (core) is not a fork but rather a reimplementation / rewrite as far as I understand > It was forked out of .NET 4.x and dropped support for a lot of things in the first versions.
>An early name for the .NET platform, back when it was envisioned as a successor to the COM platform (hence, "COM+"). Used in various places in the CLR infrastructure, most prominently as a common prefix for the names of internal configuration settings. Note that this is different from the product that eventually ended up being named COM+.
For example, see the top comment in https://github.com/dotnet/runtime/blob/main/src/coreclr/vm/o...