this post was submitted on 27 Aug 2024
128 points (96.4% liked)
Open Source
31129 readers
280 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I always thought of Mono being synonymous to dotNET . And I was not aware that Mono started that early, in 2001. Why does the WINE team takeover Mono, if its not Windows specific?
I think the WINE project was maintaining a fork of Mono that was used to support running certain Windows applications:
https://wiki.winehq.org/Mono
So in addition to translating traditional WIN32 system calls, WINE also supports .NET applications, which a number of Windows programs require.
To add to that for clarity: With the original Mono, you could run a regular Windows .net application on non-Windows without any additional work (with limitations, as native Windows API calls were unsupported). With the modern dotnet, you can compile new applications from source that will run anywhere