4 ms·
> Windows 10 also had WSL2 which made it an okay development system. To be honest, I would have preferred WSL1 which implemented the syscalls directly under Wi
by LoganDark 3y ago
> Windows 10 also had WSL2 which made it an okay development system.
To be honest, I would have preferred WSL1 which implemented the syscalls directly under Windows for the best possible integration, but they eventually just threw that away and switched to using virtual machines!
- ht85 3y agoTo be honest, I would prefer to have my guts sprayed with honey and exposed to a large colony of ants.
- rootw0rm 3y agoagreed, WSL1 was an ambitious, cool project
- dspillett 3y agoAgreed, but I could never get past the thought “all the friendliness of Unix, all the security & stability¹ of Windows”! -- [1] never trust an OS that can't reliably be left alone for 24 hours without rebooting itself while you aren't looking
- blodkorv 3y agoIf windows is certified to run the US military its secure and stable.
- dspillett 3y agoDebatable. In any case: How do I get the version+configuration used on US military installations on my machine?
- PrimeMcFly 3y agoThe stripped down very carefully configured Windows the military uses isn't the same Windows most people/businesses are using.
- lloeki 3y agoTo be fair it's quite impressive WSL1 got this far, but ultimately it was doomed from the start if one targets perfect compatibility. Given there's no "Linux specification" the spec is the actual code, nooks and crannies and all, down to nitty gritty details and implicit behaviours that end up indirectly getting relied upon. The only solution is to basically implement these in excruciating details, which may or may not possible depending on the Windows things being wrapped. Then the question of intellectual property, copyright, and licensing come in, as MS would have to ensure that it's a clean room implementation or be subject to GPL terms (cue the Oracle Java vs Android shenanigans). So at some point it makes sense to just throw a VM at the job, cleanly separating realms, sidestepping any legal landmines, and ensuring perfect compatibility, especially as the whole HyperV infrastructure is quite solid and used throughout the MS ecosystem as a general strategy, e.g the Xbox uses HyperV to isolate games and apps. Tangent: I wish (the VM part of) WSL2 would be available on Xbox, allowing one to run Linux while keeping the whole regular OS and features!
- supriyo-biswas 3y agoWine does all of that though for Windows, even when the syscall structure and caveats or compatibility fixes for the Win32 APIs are unknown. With Linux, all the syscalls and their bugs are documented, at least in the commit history, if not the man pages.
- CJefferson 3y agoWine is an amazing piece of software,but it’s still easy to find issues in many apps. Microsoft wanted something it could sell as a general Linux replacement, so it needed close to 100% compatibility.
- supriyo-biswas 3y agoMy point still stands — Linux syscalls are documented, the Win32 APIs and syscalls aren’t.
- 3y ago
- realitythreek 3y agoWSL v1 hasn’t gone anywhere. It likely won’t until they fix the issues with v2 and VPNs.
- JohnFen 3y agoI'd never used WSL1, but I use WSL2 at work (where I'm forced to use Windows). It's OK. I don't understand all the fanfare about it, though, because it's only OK. I still need to have a real Linux system around. WSL2 isn't an adequate replacement.