It's not the 'Linux on' subsystem, it's the 'Linux on Windows' subsystem, so it'd have to be Linux on Windows Windows Subsystem, which would be silly. It can't have a colon in it as some command-line tools take a subsystem as an argument, and traditionally, Windows command-line tools have used colons the same way Unix has used equals, i.e. to separate an argument name from its value, and parsing that gets harder when you're expecting colons in the value, too.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments