Live data from Hacker News

Microsoft donates the Mono Project to the Wine team

mono-project.com

291–300 of 509 posts

Re: Microsoft donates the Mono Project to the Wine team

#291

I always assumed Microsoft did not condone Wine or other re-implementations of their APIs (like ReactOS), but that they were protected by DMCA reverse engineering provisions and anyway too insignificant to send the legal team after. Wikipedia says, > Until 2020, Microsoft had not made any public statements about Wine. ... On 16 February 2005, Ivan Leo Puoti discovered that Microsoft had started checking the Windows R…

AWS Supports one of the tools for porting out of AWS. Supporting something that looks like an escape valve (whether it works or not) keeps the antitrust people off your neck.

Re: Microsoft donates the Mono Project to the Wine team

#292
post #74

Earlier quoted context omitted.

No, they pretty much gave up on winforms when .net core morphed into "the" .net that is cross platform. There are some nice crossplatform gui libs now though.

Not really. Winforms have been updated to .net core. And a bunch of handy features to modernize it have been added. I'd say it's the simplest and quickest way to go if you need to bang out a quickie app for Windows only. https://learn.microsoft.com/en-us/dotnet/desktop/winforms/?v...

If true this would be huge. I got burned on the whole silverlight, Universal Windows Platform, WPF etc. All these new and improved solutions had all sorts of issues, no designer, no or weaker accessibility stories, bloated, slow etc etc. C# + Winforms would be appealing. Some of the performance with larger datasets in the new solutions (tables etc) was just surprising. I really feel like Microsoft got so distracted chasing phones, tables, touch etc they forget just basic line of business application development which they could and should have owned.

Re: Microsoft donates the Mono Project to the Wine team

#293
post #71

https://wiki.winehq.org/Mono#Microsoft_.NET for why Mono is relevant to Wine

Thank you, I’ve been looking for an explanation of this. So Mono is useful to Wine because its users care more about licensing and running legacy software: Mono is free software and an acceptable runtime for pre-.NET 5.0 stuff.

Re: Microsoft donates the Mono Project to the Wine team

#295

Earlier quoted context omitted.

Well, to be fair .NET Standard wasn't a framework, it was a standards/compatibility label and compilation target. .NET Standard includes various versions of things that MS doesn't even touch. I stopped doing .NET stuff before .NET 5 so I'm not hugely up to date with the latest shenanigans.

But….net is everything! And also nothing ! It’s a product? It’s a suite! It’s a system ! Visual Basic .net ! What ?

Floor wax/desert topping!

https://snltranscripts.jt.org/75/75ishimmer.phtml

Re: Microsoft donates the Mono Project to the Wine team

#296

Earlier quoted context omitted.

Is there a way to build a GUI app with .NET on Linux? Will it be cross-platform?

Avalonia. The UI isn't native, is a Skia canvass with drawn controls. But it'll work on basically every OS and it's pretty good. Also, you're not writing JavaScript, so that's a win any day in my book.

Sounds like Flutter?

Re: Microsoft donates the Mono Project to the Wine team

#297
post #290

Earlier quoted context omitted.

It's been very hard to explain to my organisation that Windows Server is dead. We haven't deployed a system to it in two years, everything is some kind of dockerised linux thing but the "we're a Microsoft shop" idea prevails. In the end we decided to just let the management think what they want. I've been more of a Unix person for 40 years but I kind of miss the "good" versions of Microsoft Server - in the 1990s / ea…

I’m a Unix person and I know nothing about Windows Server. How has PowerShell made it less competitive?

It hasn't. Powershell is probably one of great things to come out of Windows Server. I still use it with *nix machines and it powers some sidecars at work. If you are stuck with Windows Server, it's only thing that gives you a fighting chance of being able to do anything NotClickOps (tm)

Sure, it's got some unique characteristic that more traditional shell users dislike but that's just a matter of taste.

Re: Microsoft donates the Mono Project to the Wine team

#298
post #290

Earlier quoted context omitted.

It's been very hard to explain to my organisation that Windows Server is dead. We haven't deployed a system to it in two years, everything is some kind of dockerised linux thing but the "we're a Microsoft shop" idea prevails. In the end we decided to just let the management think what they want. I've been more of a Unix person for 40 years but I kind of miss the "good" versions of Microsoft Server - in the 1990s / ea…

I’m a Unix person and I know nothing about Windows Server. How has PowerShell made it less competitive?

Priorities could have been better spent on bringing headless, WSL, ssh, and Terminal up to speed twenty years earlier.

Re: Microsoft donates the Mono Project to the Wine team

#299

Earlier quoted context omitted.

Windows: it's cross platform! Looks inside "Except for Linux" Huh

Contribute to the Maui backend for GTK and/or Qt, nothing is stopping you Alternatively, just because you're on .NET doesn't mean you need to use Microsoft sanctioned UI toolkits, just as C++ has no "official" UI toolkit. You're free to pick up some GTK or Qt bindings if you want a native feeling and your application is already architectures correctly. Alternatively, throw Imgui at it if you just need dev tooling, or…

I don't think it's very productive to contribute to projects that are the victim of strategic sabotage.

Re: Microsoft donates the Mono Project to the Wine team

#300

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…

For modern .NET, you don't need to know anything about the legacy terms of Mono, .NET Core, .NET Framework, .NET Standard, etc. All you need is .NET 8 SDK. It's fully-cross platform and installs support for both C# and F#.

For example, just download .NET 8 SDK on whatever platform, which is usually very easy on most platforms, and then run `dotnet fsi` to get into an F# REPL.

Post reply on HN