this post was submitted on 27 Oct 2026
113 points (84.7% liked)
Open Source
49862 readers
313 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 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You still need to run the exe through raven. Though you can do that (and it's also possible with wine already) by having the runner assotiated with
exefiles in your file browser. Normally with wine it's already the case that you can double click on the exe from there and have it launch.When they say "run directly in the CPU" what they mean is that it's not a VM.. but this was already true of wine too.
My understanding is that they are replacing the windows kernel (with help of ReactOS code) and asking you to install official Microsoft libraries into a separate runtime environment.. so it's similar to a VM in the sense that it's running a different kernel with its own runtime, but at the same time not a VM because it's not emulating the hardware level.. it's a lower level than wine but a higher level than a VM.
I feel this can potentially be more of a moving target (since it depends on Microsoft not changing the lower level ABI used in future versions of the libraries) and less legally-safe (you need to agree to MS terms when you install their libraries.. at any time they can change them and say you cannot do this).
Wine instead implements higher level APIs, which MS is incentivized to keep stable, since changes at that level would also break compatibility with programs (and in some cases, Wine's API is actually more compatible with Windows software than modern versions of Windows that have dropped older APIs).
Plus.. it necessarily relies in closed source software (the MS libraries) to run.. so I'd argue it's less free than wine.
It's more that wine tries but often fails silently for some reason, hopefully this is more user friendly and will actually just tell me "you need .net framework click here to install" and that sort of thing.
Well, it's still early, so we won't know yet how friendly, robust / stable and compatible it will be. I expect not every program will work regardless of whether you have installed the right version of the libraries or not. In the tests they are doing they say VLC for example is not starting up.
I also think that the stats showing it running better than Wine might be a bit premature too.. it's not impossible for the performance to get worse when more gets implemented in order to have wider support. But we'll see, maybe it does result in a better approach.