Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think this name would be confusing. For one - it is for linux, not windows.And it is a subsystem running Windows. So, it should be called Windows Subsystem for Linux, or WSL.


You might be missing context here.

There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM).

https://github.com/microsoft/WSL

The feature is a windows subsystem (for running Linux).


I think this may be a woosh moment where they're saying the Microsoft version should be called LSW because it's for Windows. Probably sounds more obvious with a more sarcastic tone


The concept of a "subsystem" in Windows has evolved since the operating system's inception when Windows NT was designed to support multiple operating system environments through distinct subsystems. Win32 subsystem, which features case-insensitive filenames and device files in every directory, and the POSIX subsystem, which supports case-sensitive filenames and centralized device files: Windows subsystem, the Subsystem for Unix-based Applications (SUA), and the Native subsystem for kernel-mode code were the main subsystems at first.

/SUBSYSTEM linker switch was used to specify the target subsystem at compile time, enabling applications to be compiled for different environments such as console applications, EFI boot environments, or native system processes.

In this nomenclature, WSL follows the original naming conventions (although SUA should have been called WSUA).


Watch out. You are explaining serious stuff under a comment that was essentially "watch out, your parent comment was sarcasm".


Sure, but a little education is useful as background is often lost.


I do love this sort of nerd talk!


Except WSL doesn't actually use any of the nt subsystem machinery in either of its incarnations.

And also, it doesn't really follow that nomenclature. Those all follow "user code target" Subsystem. Windows Subsystem, OS/2 Subsystem, Posix Subsystem, etc.


WSL1 used pico processes/providers, system call translation, and directly used NT Kernel Executive. I hope they resurrect it someday in the future.


that's the joke!


Jokes are supposed to be funny.


Not everybody can afford a humour bypass, good surgeons are hard to come by.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: