Microsoft donates the Mono Project to the Wine team

Original Article ↗ Hacker News Discussion ↗

Nature of the “donation”

  • Many see “donation” as “maintenance burden transfer” rather than a gift; “free as in puppies” is a recurring metaphor.
  • It’s the old Mono repo in maintenance mode for years; Microsoft keeps an actively developed fork inside dotnet/runtime for its own needs.
  • Several comments question whether there’s any financial endowment or meaningful tax write‑off; consensus is that any write‑off value is likely negligible.

Mono vs modern .NET

  • Original Mono: C‑based reimplementation of the Windows-only .NET Framework, including app domains and desktop GUI stacks like WinForms and some WPF support.
  • Modern .NET (formerly .NET Core): Microsoft’s official, cross‑platform runtime in dotnet/runtime, largely MIT/Apache licensed, high performance, and the recommended target for new development.
  • There is also a Mono-derived runtime living inside dotnet/runtime/src/mono used for mobile and WebAssembly; it has diverged (e.g., removed multi‑AppDomain support).

Why Wine cares

  • Wine wants to run legacy Windows apps targeting .NET Framework 1–4.x; Mono is the only realistic non‑Windows implementation for that.
  • Wine has long maintained its own fork (wine-mono) and used it to implement Windows .NET in Wine without shipping Microsoft’s proprietary Framework.
  • Transferring the “Mono” name and repo to Wine is seen as aligning stewardship with the main remaining use case: compatibility with old Windows .NET software.

Status and future of Mono

  • Widely described as “on life support”: few commits, behind .NET Framework 4.8, no new feature work expected.
  • Expected future: bug fixes and OS compatibility work so old .NET apps continue to run under Wine; no meaningful new APIs.
  • Some niche users remain (e.g., embedded runtimes, game engines, Second Life), but many are migrating away.

Microsoft strategy and trust

  • Some view this as pragmatic cleanup now that .NET itself is cross‑platform; Mono’s original goal has been effectively met by official .NET.
  • Others frame it as a classic “embrace/extend/extinguish” arc around Xamarin/Mono tooling and mobile/desktop stacks (Xamarin.Forms → MAUI, VS for Mac, etc.), fueling skepticism about relying on Microsoft stacks long‑term.
  • Several note Microsoft’s warmer stance toward Wine and open re‑implementations in general, citing prior legal acknowledgments and the business importance of Linux and cross‑platform .NET.