Mono is Dead. Long live... Wine?

Показать описание

Mono, the technology that enabled C# and the .NET runtime to run on platforms such as Linux, Mac, iOS and Android is dead. Well, Microsoft's stewardship of it is dead. Instead the torch is being passed to WineHQ, the makers of the popular open source Windows to Linux compatibility layer Wine.

The Mono project has been of massive importance to the world of game development. Basically if its a game engine that supports C# and runs on non-Windows platform, it most liked *used* Wine. These days though, .NET itself is cross platform, making continuation of the Mono project a lot less important.

Links
-----------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------

Рекомендации по теме

Комментарии

Haven't looked at Mono in forever.. just checked the repo and see that I'm still credited for code I wrote back in 2003. Nice.

misterkite

There is a little misunderstanding here I think. Mono became the upstream of dotnet. Modern dotnet wouldn’t exist without mono.

scotmcpherson

4:00 "Well over a decade. Maybe two decades". It was started in 1993, so it's over 3 decades now... :)

iXPilot

one thing I find most interesting is that Microsoft handed it over to WINE. It means that they are in "communication", and probably don't have a bad relationship.

whtiequillBj

"wine is an emulator or sorts". Wine HQ: Wine (originally an acronym for "Wine Is Not an Emulator")

HairyPixels

Damn, we really do live in a weird timeline.
Microsoft giving stuff to the Linux community.

safebox

Funny thing is Microsoft dropped .NET Core brand a few years ago and now it's just .NET like before but with the same features as .NET Core. I don't know why they can't name things over there.

therealgunny

One of my friend's name is Mono. The title "Mono is dead" got me worried.

AiryGallantry

Mono didn't age like a fine wi...

sicfxmusic

To be honest, I have mixed feelings about it: yes, it is useful for Wine, because it helps with legacy things, but on the other... Without WPF (GUI stuff with .NET) implementation it's not that useful and there are a lot of desktop software written with WPF. And Wine itself usually not interested in starting (new) large projects, so no WPF, MFC and so on - only the stuff which is being shipped with Windows (and still, to a some degree: not all DLLs have the priority). The motivation is understandable: to not disperse the resources (since most of the work is being done by Codeweavers), but still it's a bit sad.

iXPilot

For some reason I reflexively got nervous by the title of the video but realistically it just makes sense to pass the torch since .NET fully supports what Mono was doing. But it goes to show you how even though Microsoft is like this never ending tower that pokes through the clouds, sometimes hitting it with a pebble the right way can begin a chain reaction that disrupts it's foundation forcing the renovations into something else.

thedrunkmonkshow

I wonder if this will have any repercussions on MonoGame, or is MG separate enough from Mono to be unaffected? I also wish Microsoft hadn't dropped support for XNA - why is backwards compatability so hard to maintain?

MillisecondFalcon

Mono is always going to be remembered in our hearts

everythingcouldbesimplify

Regardless of what Wine is said to stand for, it ultimately emulates Windows funtionality.

VillageIDT

but, what will happen to all embedded mono projects? there is a C API that you can use to embed C# inside C applications, and mono not being avaliable makes me worried about the compat with those projects

sakamocat