Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft donates the Mono Project to the Wine team

mono-project.com

Post reply on HN
Print view View original

51–60 of 509 posts

Re: Microsoft donates the Mono Project to the Wine team

#51

Post by [deleted] »

tredre3 wrote: post #44
masfuerte wrote: post #37

> We want to recognize that the Mono Project was the first .NET implementation on Android, iOS, Linux, and other operating systems. Is this true? The pre-releases and version 1 of .Net came with the source for a reference implementation of the CLR that ran on Linux or BSD. I can't remember what license it had and I thought Mono was a separate project, but maybe Mono was based on it. Not that it matters now.

.Net Core 1.0 released in 2016 supports Linux yes. Lagacy .Net never supported OSes other than Windows. Mono, released in 2004, was the first attempt to bring it to other OSes.

[deleted]

Re: Microsoft donates the Mono Project to the Wine team

#52

Post by minkles »

commercialnix wrote: post #34
minkles wrote: post #32

Earlier quoted context omitted.

There are a very tiny minority of people who can choose the right technology for the job. Rust is not the answer for most problems. If you like it or not!

I write fullstack web applications in Rust, client-side too with a shim for interfacing with some JS for the DOM. So, I can agree with you in the abstract, but I'm gonna have to see you as part of the crowd that "hasn't figured it out yet".

Oh wow so you write fancy crud apps on the web? I've already got 300 people who can do that in C# (.net core) already. Why do I need any Rust people?

What I need is people who can write very complex rule and constraint engines, mathematicians and statisticians to deliver some business value, not crud monkeys.

Re: Microsoft donates the Mono Project to the Wine team

#53

Post by older »

lolinder wrote: post #49
zbowling wrote: post #31

I worked on Mono a lot back in the early 2000s (back in the SVN days before it moved to Git, even). This move makes a lot of sense. Things evolved a lot over the years. Mono's legacy goals, which are to be a portable CLR (.NET) runtime for platforms that Microsoft didn't care about, don't make much sense today. Mono made a lot of sense for running places where full .NET didn't, like in full AOT environments like on t…

Is there somewhere where someone new to the ecosystem can get a simple introduction to all of these different terms and which ones are still relevant today? I looked into .NET somewhat recently and came away with the apparently mistaken impression that Mono was how .NET did cross-platform. I guess I must have been reading old docs, but I'm pretty sure they were at least semi-official. Is there good documentation some…

This is the official one: https://learn.microsoft.com/en-us/shows/visual-studio-code/g...

Re: Microsoft donates the Mono Project to the Wine team

#54

Post by rererereferred »

Wytwwww wrote: post #35
donatj wrote: post #11

Is the correct interpretation, reading between the lines that the original Mono project is being retired, and basically put on life support?

I think this has already been the case for years? Mono didn't really have much of a point after MS opensource .NET and ported it to other platforms.

And Wine will probably not do much more than maintenance so applications targeting .net 1-4 work on Wine.

Re: Microsoft donates the Mono Project to the Wine team

#55

Post by Phrodo_00 »

dtquad wrote: post #38
rickcarlino wrote: post #12

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?

Microsoft's own FOSS multiplatform implementation of the .NET runtime is now much more performant and feature complete than Mono. However Mono is easier to embed into other applications and easier to port to new platforms. That is for example why it's used for the .NET/Blazor WebAssembly stuff. Microsoft still maintains their own fork of Mono for this specific use case. Mono also implements some of the legacy Windows…

Mono also supports winforms. I don't think they're supported in dotnet (but there's libraries for Gtk, although you could also use Vala with a bit extra effort).

Re: Microsoft donates the Mono Project to the Wine team

#57

Post by Blot2882 »

lolinder wrote: post #49
zbowling wrote: post #31

I worked on Mono a lot back in the early 2000s (back in the SVN days before it moved to Git, even). This move makes a lot of sense. Things evolved a lot over the years. Mono's legacy goals, which are to be a portable CLR (.NET) runtime for platforms that Microsoft didn't care about, don't make much sense today. Mono made a lot of sense for running places where full .NET didn't, like in full AOT environments like on t…

Is there somewhere where someone new to the ecosystem can get a simple introduction to all of these different terms and which ones are still relevant today? I looked into .NET somewhat recently and came away with the apparently mistaken impression that Mono was how .NET did cross-platform. I guess I must have been reading old docs, but I'm pretty sure they were at least semi-official. Is there good documentation some…

Mono was, but newer versions of .NET run on Linux and Mac.

You can install at the link below, and then making a project is just `dotnet new console` and run with `dotnet run`

https://learn.microsoft.com/en-us/dotnet/core/install/linux

Re: Microsoft donates the Mono Project to the Wine team

#58

Post by masfuerte »

saurik wrote: post #50
masfuerte wrote: post #37

> We want to recognize that the Mono Project was the first .NET implementation on Android, iOS, Linux, and other operating systems. Is this true? The pre-releases and version 1 of .Net came with the source for a reference implementation of the CLR that ran on Linux or BSD. I can't remember what license it had and I thought Mono was a separate project, but maybe Mono was based on it. Not that it matters now.

You are thinking of Rotor. FWIW, I also feel as if Portable.NET--which was rebranded at some point to DotGNU when I think it was even donated to the FSF--had predated Mono in functioning? The Mono website has an archive of an old mailing list post which at the time talks about even-older origin of the project. It is (of course) heavily biased for Mono, and hilariously gives me an awkward shout out ;P. https://www.mon…

Thank you!

So it ran on Windows, FreeBSD and Mac OS X making it the first non-Windows implementation of .Net, but it didn't run on Linux. It also had a fairly useless licence, so Mono was separate.

https://en.wikipedia.org/wiki/Shared_Source_Common_Language_...

Edited to add: and thanks for the link. Only three developers and there's already drama! :-)

Re: Microsoft donates the Mono Project to the Wine team

#59

Post by bmacho »

ragebol wrote: post #43
jcims wrote: post #22

Earlier quoted context omitted.

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

I'm not a dog person: a puppy would be a burden (financially and time-wise) and provide me barely any fun.

That's what ’free as in puppies’ mean.

Free software is typically described as "free as in freedom" or "free as in free beer". (This is probably a limitation of English tho, my language has 2 different words for permissions and costlessness.) GP above proposes the "free as in puppy" variant, which means that it is a burden of maintenance. I can't recall any real examples for this.

Re: Microsoft donates the Mono Project to the Wine team

#60

Post by bawolff »

jcims wrote: post #22
rickcarlino wrote: post #12

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?

I love this. Definitely using this next time someone tries to guilt me into becoming maintainer of some abandonware foss project.
Post reply on HN