Microsoft donates the Mono Project to the Wine team

Post by nickcox » Wed, Aug 28, 2024, 6:57 AM UTC

safety1st wrote: post #309

bmitc wrote: post #300

Earlier quoted context omitted.

For modern .NET, you don't need to know anything about the legacy terms of Mono, .NET Core, .NET Framework, .NET Standard, etc. All you need is .NET 8 SDK. It's fully-cross platform and installs support for both C# and F#. For example, just download .NET 8 SDK on whatever platform, which is usually very easy on most platforms, and then run `dotnet fsi` to get into an F# REPL.

This is wild, apparently this stuff is in the Debian repos now? https://learn.microsoft.com/en-us/dotnet/core/install/linux-... So you can just apt install dotnet-sdk-8.0. This must be the most unfriendly Linux install documentation I've ever seen though, it was not easy to find the names of those packages.

Post by erremerre » Wed, Aug 28, 2024, 7:19 AM UTC

RadiozRadioz wrote: post #303

kelnos wrote: post #108

Earlier quoted context omitted.

I think Microsoft has finally realized that its animus toward projects like Wine and pre-acquisition Mono was ultimately unproductive, and a net negative for Microsoft itself. I still don't trust MS's motives in general, but I think they at least recognize that Wine/Proton helps make the Win32 and DirectX APIs a sort of de-facto cross-platform standard when it comes to things like desktop gaming, and that this is a g…

> Wine/Proton helps make the Win32 and DirectX APIs a sort of de-facto cross-platform standar There are perfectly fine _actual_ cross-platform standards like Vulcan and OpenGL. If your goal is cross-platform, making a Windows app that you hope will be converted well enough is a strange way to approach it.

Post by register » Wed, Aug 28, 2024, 7:32 AM UTC

mixmastamyk wrote: post #296

aspeckt112 wrote: post #165

Earlier quoted context omitted.

Avalonia. The UI isn't native, is a Skia canvass with drawn controls. But it'll work on basically every OS and it's pretty good. Also, you're not writing JavaScript, so that's a win any day in my book.

Sounds like Flutter?

Post by drw85 » Wed, Aug 28, 2024, 7:45 AM UTC

hsbauauvhabzb wrote: post #154

lolinder wrote: post #49

Earlier quoted context omitted.

Is there somewhere where someone new to the ecosystem can get a simple introduction to all of these different terms and which ones are still relevant today? I looked into .NET somewhat recently and came away with the apparently mistaken impression that Mono was how .NET did cross-platform. I guess I must have been reading old docs, but I'm pretty sure they were at least semi-official. Is there good documentation some…

You’re not alone. I would say I’m not ‘new’ and even developed .net 4.5 for a number of years. I’m just as stumped by the naming mess that Microsoft made across the board in that space. Edit: I say 4.5 because I mean the original thick .net which is not dotnet core, which I think is the way to differentiate between versions, but also all the sub libraries like the orm were iirc named the same but did different things…

  - .NET Framework
  - .NET core 1
  - .NET core 2
  - .NET core 2.1
  - .NET core 3
  - .NET 5+

Post by rahkiin » Wed, Aug 28, 2024, 7:55 AM UTC

tomkarho wrote: post #306

bmitc wrote: post #300

Earlier quoted context omitted.

For modern .NET, you don't need to know anything about the legacy terms of Mono, .NET Core, .NET Framework, .NET Standard, etc. All you need is .NET 8 SDK. It's fully-cross platform and installs support for both C# and F#. For example, just download .NET 8 SDK on whatever platform, which is usually very easy on most platforms, and then run `dotnet fsi` to get into an F# REPL.

> It's fully-cross platform To a point. Making cross platform native desktop apps is still in the hands of 3rd party vendors such as Avalonia and Uno. MAUI was supposed to fix that oversight to a less than stellar results.