4 ms·

The way to parse WSL is that it's a <Windows (NT) Subsystem> for Linux. Windows NT had environment subsystems as a key part of its architecture, with subsystem

The way to parse WSL is that it's a <Windows (NT) Subsystem> for Linux. Windows NT had environment subsystems as a key part of its architecture, with subsystems for POSIX and OS/2, originally[1], and even Win32 was conceptually a subsystem for NT, albeit a very important one. [1] https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/media/File:Windows_2000_architecture.svg https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/me...

skohan 5y ago
And how are you supposed to parse the rust library?
- deleted 5y ago
  [deleted]
- gpm 5y ago
  <A Rust Library> for Windows
  - remram 5y ago
    That still sounds like it's a Rust library you get to use on Windows, not a library of Windows functions to use from Rust.
- moron4hire 5y ago
  A Rust Binding for WinAPI
  - skohan 5y ago
    That doesn't even contain "Rust for Windows"
    - uranusjr 5y ago
      Shirley you realise WinAPI is officially named the Windows API?
      - skohan 5y ago
        Yeah but MS could actually call this library what it is, not leave it to multiple levels of inference. And don't call me Shirley!
deleted 5y ago
[deleted]
antibuddy 5y ago
> The way to parse WSL is that it's a <Windows (NT) Subsystem> for Linux. For me that still parses wrong on first try. I mean I can make sense of it, because I already know how it is meant, however for me the most obvious assumption is, that it is for the given host and that host is Windows, not Linux. So Linux (compatibility) subsystem for Windows would make more sense to me.
- harles 5y ago
  I think rearranging those words in almost any other order would’ve been superior: WLS, LSW, LWS
vbezhenar 5y ago
And the fun part is that since WSL 2 it's no longer a Windows Subsystem, but just a Linux kernel in VM with some nice integrations with host Windows OS.