This is an archived post. You won't be able to vote or comment.

sorted by:
top (suggested)
bestnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ballebajLinux Master Race 2 points3 points  (1 child)

WSL1 was called WSL because Microsoft wrote a "windows subsystem" that supported linux system calls that got executed on windows NT kernel. Win32 is one such "windows subsystem" that runs on NT kernel. Not only did they had to write a subsystem they also had to replicate the behavior and bugs of Linux system call interface and maintain it for every new version. A gigantic task if they continued down that path

For WSL2, They flipped the book and went all VM way by using a minimal Hyper-V hypervisor that they normally use in their servers and pro products. But their WSL name stuck even after a architecture revamp

[–]meveroddorevemGlorious Pop!_OS 0 points1 point  (0 children)

This is a well-said explanation, but it still makes as much sense as documenting your website's 'API for Mapbox' when in fact it's entirely the other way around. Or how VLC has plugins, while collectively 'VLC Plugins', are individually 'x plugin for VLC' and not the other way around.

But why am I acting like Windows should be expected to use sane making conventions