Wine Releases Framework Mono 6.14

Today marks the release of Framework Mono 6.14, the first major Mono release in five years and the first under WineHQ's stewardship. This update includes long-awaited improvements such as native macOS ARM64 support, enhancements to System.Windows.Forms for X11, better COM interface support, and various stability fixes. Phoronix reports: In addition to the native macOS ARM64 support and System.Windows.Forms improvements for X11, some of the other Mono 6.14 improvements carried out over the past half-decade include improved support for generated COM interfaces, many warning fixes, addressing common cases where processes would hang on exit, and more.

As for the "Framework Mono" name rather than just Mono, the release announcement explains: "Framework Mono is the project previously hosted at https://github.com/mono/mono, which was then simply called Mono. I have made this change to distinguish it from 'monovm' and 'Wine Mono', which are different projects. Framework Mono is a cross-platform runtime compatible with .NET Framework." You can download and learn more about the release here.

Why

[Latent Heat]

OK, OK, yeah, yeah and yeah, but why this instead of OpenJDK apart from, say, the renegade Klingon or is he a Khan wannabe?

DOES NOT BUILD - this is crap

[gavron]

Yeah they announce. Announce a failure. Seriously this is just crap.

it doesn't build.

The Readme.md is lacking any useful instructions.

The ./configure takes over an hour on a 16-core kickass laptop.

make has errors. Like the kind any programmer woulc have fixed in 5 seconds but couldn't be bothered to.

sudo make install fails.

This is crap.

Re:

[bill_mcgonigle]

Thanks for the head's up.

Looks like more of an announcement of a project than a release.

The way it was summarized doesn't really match the site.

I was just hoping I wouldn't have to restart Jellyfin every night with cron. It leaks about 4GB a day with minimal usage.

Re:

[ledow]

So when can we expect your patch?

What's the use-case?

[Guspaz]

What would somebody actually use "Framework Mono" for? As in, what use case is there for this specific variant of it instead of using Microsoft's current mono fork (https://github.com/dotnet/runtime/tree/main/src/mono) or Wine Mono (https://gitlab.winehq.org/mono/wine-mono)?

Re:

[brunoblack]

My first thought too. Doesn't that MS stuff run natively on Linux nowadays?

Windows Forms apps on non-Windows OS

[tepples]

Microsoft has declined to merge an implementation of System.Windows.Forms for any platform other than Windows. From CONTRIBUTING.md [github.com]:

Whilst most .NET Core/.NET components are cross-platform Windows Forms implementations remain tightly coupled with Win32 API. With this we will typically not accept contributions that provide cross-platform implementations.

Re:What's the use-case?

[caseih]

The official MS dotnet release for Linux does not include any sort of WinForms implementation. I have an app I occasionally run on Linux that is WinForms and it works alright under Mono and it's cross-platform WinForms implementation.

Does anyone remember

[trelanexiph]

~15-20 years ago Miguel de Icaza ranting about how terrible Open Source is? RMS even called him a traitor.
Why? Miguel constantly pushed Mono and lambasted everyone who disagreed with him or even refused to use C#. When that didnâ(TM)t work he ran off to the safety of Microsoft.

Re:

[Locutus]

When C++ and OOP were starting to go strong I met a guy showing a desktop environment for Linux called Gnome. When I asked about what was great about it he said it was like object-like. Now I'd run UNIX, DOS, Windows, Solaris, HPUX and OS/2 and CORBA was starting to spread its wings too so I didn't get why someone on a *nix platform wouldn't be doing full blown OOP. So I quizzed him more and he went off on how much like Microsoft's COM, and possibly DCOM it was. He clearly held Microsoft up on a pedestal.

Re:

[caseih]

Gnome was originally based on CORBA if I recall. Had nothing to do with COM or DCOM, other than being vaguely similar in idea. CORBA was an open standard and was already available on several platforms. Gnome abandoned it after Gnome 2 I think. It was an interesting idea. Embedding the file browser in an app, or the web browsing engine. But turns linking in a component library works just as well as trying to build up an app at run time using CORBA.

I think KDE still uses a system not unlike what Gnome had

Re:

[jgfenix]

Gnome's Bonobo was basically an OLE2's clone using CORBA instead of COM.

Bonobo specifies a number of such contracts, or interfaces, as they are usually called. The Bonobo interfaces were inspired by Microsoft's OLE2 [3]. Microsoft uses OLE2 for interconnecting components in the Windows-environment. Bonobo is not an implementation of OLE2, however. Many of the design decision that went into OLE2 were re-evaluated, and all Windows-specific parts had to be adapted for Unix and the X Window System. And importan