81–90 of 509 posts
.NET now runs on Linux and other platforms, so what is the purpose of maintaining Mono separately at this point?
Mono can run old .NET framework applications directly.
Earlier quoted context omitted.
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".
Every program I've seen like that is terribly inaccessible. "Doesn't expose headings to screen readers" levels of inaccessible. And yes, you can do a whole lot of working around that, but you know what I'd do? Section heading I like Rust, but please don't write a website in it.
What is the mono logo? a gorilla with a hat? or a pile of poop? serious question.
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…
I know little of dotnet beyond trying various semirandom things to make some .net apps work on linux. With that out of the way, my understanding is that - Originally there was .Net Framework, by microsoft, for windows only. Versions 1.0 -> 4.8 were released. - Then mono came along as a somewhat clean-room reimplementation of .Net framework, focusing on making it run on Linux. Though mono does not implement windows gu…
While Microsoft doesn't have their own framework supporting Linux GUI apps on the modern .NET runtime (MAUI does Mac/iOS/Android but not Linux), there are third-party ones like Avalonia.
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…
I know little of dotnet beyond trying various semirandom things to make some .net apps work on linux. With that out of the way, my understanding is that - Originally there was .Net Framework, by microsoft, for windows only. Versions 1.0 -> 4.8 were released. - Then mono came along as a somewhat clean-room reimplementation of .Net framework, focusing on making it run on Linux. Though mono does not implement windows gu…
It is harmful to write new code that targets .NET Framework and existing actively maintained applications all have migrated to .NET. The ones that did not either have poor maintenance or authors that lack time as they don't owe extra effort unless they want to do that (or sometimes it is a skill issue, unfortunately).
Earlier quoted context omitted.
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]
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…
I know little of dotnet beyond trying various semirandom things to make some .net apps work on linux. With that out of the way, my understanding is that - Originally there was .Net Framework, by microsoft, for windows only. Versions 1.0 -> 4.8 were released. - Then mono came along as a somewhat clean-room reimplementation of .Net framework, focusing on making it run on Linux. Though mono does not implement windows gu…
It was called .NET Core until they officially retired the .NET Framework (ie v4) by releasing .NET 5.
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 no reason to live anymore This isn't really true. Mono functions as a complete replacement for the ".NET Framework" - something that can be used to run any .NET app, including "legacy" apps targeting old ".NET Framework" versions, on any supported platform, even when the app was built to target Windows. dotnet/runtime is intended to run more modern applications that target ".NET Core" - basically, stuff th…
What is the mono logo? a gorilla with a hat? or a pile of poop? serious question.
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…