The Windows Subsystem for Linux is now open source
The Windows Subsystem for Linux is now open source
Today we’re very excited to announce the open-source release of the Windows Subsystem for Linux. This is the result of a multiyear effort to prepare for this, and a great closure to the first ever issue raised on the Microsoft/WSL repo:Windows Developer Blog
obvs
in reply to abobla • • •I wish they'd open source the name.
It should be called the "Linux Subsystem for Windows".
ReakDuck
in reply to obvs • • •fakeplastic
in reply to obvs • • •randomcruft
in reply to fakeplastic • • •On Windows MS may not call it Defender for Windows… but for Azure, it’s Defender for Cloud, Defender for Containers, Defender for SQL Databases, etc.
Microsoft Defender for Cloud overview
So really it’s just more of Microsoft’s generally crappy naming conventions… I’m looking at you Entra ID!!
edit: added link
🙂
Microsoft Defender for Cloud Overview - Microsoft Defender for Cloud
learn.microsoft.comNanook
in reply to randomcruft • •Zagorath
in reply to fakeplastic • • •If I say "the life support system for the USS Enterprise", nobody thinks that that's a system running on the life support that gives you the USS Enterprise. It's a system running on the USS Enterprise that gives you life support. Windows Subsystem for Linux sounds like it's a system running on Linux that gives you access to Windows.
HumanPenguin
in reply to Zagorath • • •Unfortunately contact mean that example dose work both ways.
If we say enterprise system for life support. People will also understand.
But voyager system for enterprise could apply either way. To be fitted to enterprise or allow enterprise activity on voyager. Or voyager activity on enterprise. For is just bad language in this context.
Here Microsoft should've used a possessive. Voyagers enterprise support system would be more normal.
Or Windows Linux support system.
But marketing and a history of no other OS matters means Mickey$oft insists on it's own layout. Over language clarity.
unwarlikeExtortion
in reply to fakeplastic • • •It's a Linux subsystem for Windows. As in, you run Windows and within it run Linux. Thus Linux is the sub-system, while Windows is the "overarching" system. Therefore, it's Linux running as a subsystem on a Windows machine. Therefore, a Linux subsystem on/for Windows.
\
That was just setting the two viewpoints equal.
Now, to add why this one is more "correct": when talking about Windows (or Linux or anything else fir that matter) subsystems, you don't call the Windows file system the Windows subsystem for Files or the Windows subsystem for Networking or Linux subsystem for RNG - You call them the filesystem, the networking system or the RNG system. And since none of them get the "for host" suffix, it seems natural to assume it't te guest system that's the "sub" system, with the other one being the whole.
Badabinski
in reply to abobla • • •From the repo's CONTRIBUTING.md:
Meh, a permissive license + a copyright transfer means this shit is just a potential rugpull. MSFT can change the license of the project to source-available or even proprietary at any time and you'll be powerless to stop it.
schnurrito
in reply to Badabinski • • •Badabinski
in reply to schnurrito • • •