Live data from Hacker News

Microsoft donates the Mono Project to the Wine team

mono-project.com

21–30 of 509 posts

Re: Microsoft donates the Mono Project to the Wine team

#21

I feel like I’m missing some context here. Is this a “free as in take this puppy” situation? How do the wine developers benefit from this?

I think it's just hurting someone at Microsoft less if they give it a home that isn't /dev/null.

Edit: quick hat tip to Mono.Cecil which I've used a couple of times to crack .Net components to bypass licensing code. It's not that we didn't pay for them but we couldn't be bothered to deal with license deployment and maintenance.

Re: Microsoft donates the Mono Project to the Wine team

#23
post #7

[flagged]

Perhaps us C programmers should be telling the Rust programmers to stop shitting up the industry for everyone else because "C" is too hard to get right? Really, point aside, there is no place for zealots and many places for a rational decision analysis in what tools to use. Absolutes and extremism are all bad.

[flagged]

Re: Microsoft donates the Mono Project to the Wine team

#25
post #10

[flagged]

> If Rust is "too hard", find some other profession and stop shitting up the industry for everyone else. If you really like Rust you should promote it by using it to write great tools that inspire others to use it, instead of shitting on people who use other tools to do actual work.

[flagged]

Re: Microsoft donates the Mono Project to the Wine team

#27
post #17

Earlier quoted context omitted.

Mono was the .net implementation for Linux (and others ?) years ago while microsoft published the windows .net runtime Since then, microsoft supports https://github.com/dotnet/runtime , which is MIT licensed Mono has no reason to live anymore, hence the lack of commits and contributions It is a dead project, I wonder what winehq has in mind here edit: as pointed by the comments, mono supports .net runtime before the…

Mono has support for app domains (and is in general closer to .NET Framework), a more powerful C API and runs on more architectures.

This must be the reason. Wine seeks to be compatible with a bunch of legacy software, some of which will want to use the equivalent of .NET 1, 2, 3, and 4.x Framework and not just "dotnet core". (Or whatever the new thing is called in Microsoftese this week.)

Edit: maybe this means WPF can be the best way to write Linux applications. After all, Win32 is the stable Linux API... nudge nudge, wink wink. :-D

Re: Microsoft donates the Mono Project to the Wine team

#29
post #22

I feel like I’m missing some context here. Is this a “free as in take this puppy” situation? How do the wine developers benefit from this?

How has ’free as in puppies’ not reached its rightful place on the podium?

Because nobody wanted to maintain it.

Re: Microsoft donates the Mono Project to the Wine team

#30

I feel like I’m missing some context here. Is this a “free as in take this puppy” situation? How do the wine developers benefit from this?

Wine has (or used to have anyway, not sure if it still does) a version of Mono it used to run .NET stuff within Wine; I'd assume this has to do with that, that they were relatively alone in having a continuing interest in the Mono codebase vs. the dotnet core stuff.
Post reply on HN