4 ms·
WSL (Windows Subsystem for Linux) isn't virtualized, as the article states. https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overvie
by notum 9y ago
WSL (Windows Subsystem for Linux) isn't virtualized, as the article states.
https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/ https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subs...
It's aim is to run Linux binaries natively. The degree of it's usefulness, issues and filesystem interoperability was discussed before so won't get into that.
- Drakim 9y agoSo it's sorta like a reverse WINE?
- notum 9y agoSort of? Exactly! Windows Is Not an Emulator!
- Piskvorrr 9y agoEmulator Not Is Windows, to be precise.
- cerved 9y agoAwesome! Can't wait to install linux on WINE
- JoBrad 9y agoWine does work in WSL, so you can install WSL on your Windows box, then use WINE to run a Windows app on the Linux instance on your Windows box.
- sevensor 9y agoAre people doing this to play Win9x-era games? I find Wine does a better job being compatible with old Win32 applications than Windows does.
- Doxin 9y agoDon't most win9x games also run on DOS? because in that case dosbox is a great solution. I might be misremembering DOS/9x compatibility though.
- danieldk 9y agoOnly sort of. WINE has a much larger scope, because it has to reimplement the complete Win32 API, because it is proprietary and cannot be redistributed. Windows Subsystem for Linux, on the other hand, 'only' needs to support the ELF loader and Linux system calls and can then use glibc, and other core libraries. Another difference is that WINE runs completely in user land, while the WSL Linux syscall handling runs in kernel land (lxcore, lxss). Probably another good comparison is Linux compat in the BSDs, which implement Linux system calls, signal handling, etc. but can use glibc and other core libraries from a Linux distribution.