4 ms·
It's an unfair fear since architecturally Wine sits at the same position as the Win32 API on Windows, which also in the end merely uses the underlying native sy
by samus 7mo ago
It's an unfair fear since architecturally Wine sits at the same position as the Win32 API on Windows, which also in the end merely uses the underlying native system calls. The only difference is that Linux aims to keep its system call interface stable.
- tracker1 7mo agoYou're saying that Windows' system interfaces aren't stable? In comparison to Linux?
- ConceptJunkie 7mo agowin32 dates back to 1993. OP doesn't know Windows history. Maintaining backwards compatibility was always a huge priority for Microsoft, even if it couldn't be perfect. If a program didn't work on a newer version of Windows, there's a good chance it was doing something unsupported.
- samus 7mo agoThe API underneath the Win32 API, the Windows Native API, is not necessarily stable and therefore not intended for direct consumption by applications.
- tracker1 7mo agoIf you're utilizing undocumented APIs that aren't meant for public use, sure... but the core Win32 APIs have been pretty stable for going on 3+ decades now. You can take a lot of win32 apps from the early 90's and they'll run without modification in windows today... though, they'll probably run in Wine and likely a better chance there... but still.
- samus 7mo agoI fully agree with that. Sadly there is always the odd application out there that uses the lower level stuff and is therefore tricky to get to run on Wine. Or more recent Windows versions for that matter.