I guess it’s simply the framing: It was a not very actively maintained open source project. So they’ve decided to turn it over to a new maintainer. Calling that ‘donation’ is a bit pushing it
Most of the time a company does something like this they would just let it die. It’s good that Microsoft have at least made the effort to hand it over to a team who’s willing to keep it going.
It’s certainly good, I’m not arguing that. My point is, if the wine team is interested, they can fork the unmaintained project, and work on that. Eventually, people will switch over to the active fork. What Microsoft is doing, is helping the process along, and making it easier. So it’s good, and helpful - but not really a “donation” to winehq.
.NET runs natively on Linux since quite some time. Honestly, I don’t get what Mono is even good for these days. Maybe reverse engineering old .NET versions.
.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That’s pretty much it. Anything new should go straight to .net core.
When I moved my personal laptop to Linux I needed WINE to run some source-available .NET apps that were written targeting the Windows-only .NET Framework
Well they said .NET Framework, and I also wouldn’t be surprised if they more or less wrapped that up - .NET Framework specifically means the old implementation of the CLR, and it’s been pretty much superseded by an implementation just called .NET, formerly known as .NET Core (definitely not confusing at all, thanks Microsoft). .NET Framework was only written for Windows, hence the need for Mono/Xamarin on other platforms. In contrast, .NET is cross-platform by default.
What’s the twist? There must be some reason.
I guess it’s simply the framing: It was a not very actively maintained open source project. So they’ve decided to turn it over to a new maintainer. Calling that ‘donation’ is a bit pushing it
Most of the time a company does something like this they would just let it die. It’s good that Microsoft have at least made the effort to hand it over to a team who’s willing to keep it going.
…Like MS-DOS getting open sourced. It’s pretty much worthless unless you need to use some really old device.
It’s certainly good, I’m not arguing that. My point is, if the wine team is interested, they can fork the unmaintained project, and work on that. Eventually, people will switch over to the active fork. What Microsoft is doing, is helping the process along, and making it easier. So it’s good, and helpful - but not really a “donation” to winehq.
Actually, wine used to maintain a fork.
So it’s like “gifting” someone a puppy.
.NET runs natively on Linux since quite some time. Honestly, I don’t get what Mono is even good for these days. Maybe reverse engineering old .NET versions.
.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That’s pretty much it. Anything new should go straight to .net core.
Only
.NET Core
sadlyWhen I moved my personal laptop to Linux I needed WINE to run some source-available .NET apps that were written targeting the Windows-only
.NET Framework
All the new stuff is now on .NET Core/5.0 and up at least.
Hasn’t been called “.NET Core” since 3.1
Although it’s essentially the subsequent version of core, .NET 5 is the successor to both .NET Core 3.1 and .NET Framework 4.
Since then, it’s just been called .NET 5/6/7/8/…
Cost cutting.
Probably simply that they are done with it (mono specifically, and possibly .net framework in the long run)
I would be extremely surprised if they are planning to abandon .NET
With ICAAN introduction of new gTLDs now they can drop .NET and pick up .ONLINE
Underrated comment.
Well they said .NET Framework, and I also wouldn’t be surprised if they more or less wrapped that up - .NET Framework specifically means the old implementation of the CLR, and it’s been pretty much superseded by an implementation just called .NET, formerly known as .NET Core (definitely not confusing at all, thanks Microsoft). .NET Framework was only written for Windows, hence the need for Mono/Xamarin on other platforms. In contrast, .NET is cross-platform by default.