Live data from Hacker News

Testing the Windows Subsystem for Linux

blogs.msdn.microsoft.com

11–20 of 142 posts

Re: Testing the Windows Subsystem for Linux

#14
post #2

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

MS is horrible at naming things, WOW64 anyone?

Or the needless confusion when everything needed to have .NET tacked onto the name.

Or after they bought Skype, and rebranded the unrelated Lync as Skype for Business. Not to mention that Lync is a homophone of LINQ, which was coming out around when Office Communication Server became Lync...

Or lately, when you had Visual Studio 2015, and what is now Visual Studio 2017 being called Visual Studio '15 while it was pre-release.

Naming things is hard.

Re: Testing the Windows Subsystem for Linux

#15
post #8
post #2

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

It's still the Windows kernel. No Linux kernel here. Just Linux userspace. The name may not sound good, but it's technically accurate. :)

Maybe it should be Windows subsystem for GNU

Re: Testing the Windows Subsystem for Linux

#17
post #11

Earlier quoted context omitted.

GNU/NT

Isn't that Cygwin?

Cygwin is also GNU/NT.

If you like, it's the same as the ways of running GNU on the FreeBSD kernel; there's Debian/kFreeBSD, which is Debian compiled against the FreeBSD ABI, and there's the Linux compat layer that can run Linux ELF binaries unmodified. Both of those are legitimately GNU/FreeBSD systems (or subsystems).

Re: Testing the Windows Subsystem for Linux

#20
post #2

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

Try: "Window's Subsystem for Linux" instead of "Windows Subsystem for Linux" and see if that helps. It's still grammatically shit.

Now who can come up with the justification for an abbreviation of "whine"?

Post reply on HN