3 ms·
Anyone else reading the title as the reverse of what it actually is? I thought it's something for running (some parts of) MacOS on Linux. Not the other way rou
by nottorp 4y ago
Anyone else reading the title as the reverse of what it actually is?
I thought it's something for running (some parts of) MacOS on Linux. Not the other way round.
- jagged-chisel 4y agoSame here. But it does follow WSL naming.
- andybak 4y agoYes. It's using the same naming as WSL which always confused me: Q: Why the same naming scheme as WSL? A: It's a proof of concept name only. If I were to distribute this as a finished piece of software, which I probably won't (see why below) I would choose a different name.
- unsafecast 4y agoIt's not confusing once you know where it came from. The NT kernel has a concept called “environment subsystems”. Win32 was, until WSL1, the only one used (a long time ago there was SFU, the grandfather of WSL). So WSL is a Windows subsystem made for Linux. Hence the name. Note that WSL2 isn't an NT subsystem, they're just using an actual kernel now. The name stuck though.
- tzs 4y agoThe original NT subsystems were for OS/2, POSIX, and Win32 and were called simply the "OS/2 Subsystem", "POSIX Subsystem", and "Win32 Subsystem". If they had stuck with the sensible NT naming convention, WLS would have simply been the Linux Subsystem.
- unsafecast 4y agoFair point. I was just arguing that it technically makes sense. The naming thing kind of started with SFU though.
- nottorp 4y agoYeah well, I'm not familiar with their naming scheme, I've managed to mostly ignore Windows in the past 10+ years. Except that legacy vb.net project... sigh, the things I'll do for money.