4 ms·

Missed opportunity to call it "Linux Subsystem for Windows", or LSW in short.

by userbinator 1y ago

riedel 1y ago
If wine was LSW1 than this is LSW2
- cheema33 1y ago
  I think this is accurate. WSL v1 did not use a VM, just like Wine. However both WSL v1 and Wine struggled with compatibility issues. WSL 2 gave up and used a VM instead. You pay a performance penalty but compatibility issues mostly go away.
  - Zardoz84 1y ago
    Well, I discrepe a lot with the "compatibility issues" of Wine... Essentially when sometimes can run better and with less issues legacy software that modern Windows.
    - cheema33 1y ago
      Example: My company uses MS Teams for meetings. Wine cannot run it reliably.
      - monocasa 1y ago
        Counter example: my windows 10 machine can't play my copy of crysis, but my Ubuntu machine can under wine.
      - ClikeX 1y ago
        To be fair. Neither can my MacBook, and that is an official release.
archargelod 1y ago
I think this name would be confusing. For one - it is for linux, not windows.And it is a subsystem running Windows. So, it should be called Windows Subsystem for Linux, or WSL.
- charrondev 1y ago
  You might be missing context here. There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM). https://github.com/microsoft/WSL https://github.com/microsoft/WSL The feature is a windows subsystem (for running Linux).
  - Neywiny 1y ago
    I think this may be a woosh moment where they're saying the Microsoft version should be called LSW because it's for Windows. Probably sounds more obvious with a more sarcastic tone
    - mycall 1y ago
      The concept of a "subsystem" in Windows has evolved since the operating system's inception when Windows NT was designed to support multiple operating system environments through distinct subsystems. Win32 subsystem, which features case-insensitive filenames and device files in every directory, and the POSIX subsystem, which supports case-sensitive filenames and centralized device files: Windows subsystem, the Subsystem for Unix-based Applications (SUA), and the Native subsystem for kernel-mode code were the main subsystems at first. /SUBSYSTEM linker switch was used to specify the target subsystem at compile time, enabling applications to be compiled for different environments such as console applications, EFI boot environments, or native system processes. In this nomenclature, WSL follows the original naming conventions (although SUA should have been called WSUA).
      - jraph 1y ago
        Watch out. You are explaining serious stuff under a comment that was essentially "watch out, your parent comment was sarcasm".

Missed opportunity to call it "Linux Subsystem for Windows", or LSW in short.

riedel 1y ago

If wine was LSW1 than this is LSW2

cheema33 1y ago
I think this is accurate. WSL v1 did not use a VM, just like Wine. However both WSL v1 and Wine struggled with compatibility issues. WSL 2 gave up and used a VM instead. You pay a performance penalty but compatibility issues mostly go away.
- Zardoz84 1y ago
  Well, I discrepe a lot with the "compatibility issues" of Wine... Essentially when sometimes can run better and with less issues legacy software that modern Windows.
  - cheema33 1y ago
    Example: My company uses MS Teams for meetings. Wine cannot run it reliably.
    - monocasa 1y ago
      Counter example: my windows 10 machine can't play my copy of crysis, but my Ubuntu machine can under wine.
    - ClikeX 1y ago
      To be fair. Neither can my MacBook, and that is an official release.

archargelod 1y ago

I think this name would be confusing. For one - it is for linux, not windows.And it is a subsystem running Windows. So, it should be called Windows Subsystem for Linux, or WSL.

charrondev 1y ago
You might be missing context here. There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM). https://github.com/microsoft/WSL https://github.com/microsoft/WSL The feature is a windows subsystem (for running Linux).
- Neywiny 1y ago
  I think this may be a woosh moment where they're saying the Microsoft version should be called LSW because it's for Windows. Probably sounds more obvious with a more sarcastic tone
  - mycall 1y ago
    The concept of a "subsystem" in Windows has evolved since the operating system's inception when Windows NT was designed to support multiple operating system environments through distinct subsystems. Win32 subsystem, which features case-insensitive filenames and device files in every directory, and the POSIX subsystem, which supports case-sensitive filenames and centralized device files: Windows subsystem, the Subsystem for Unix-based Applications (SUA), and the Native subsystem for kernel-mode code were the main subsystems at first. /SUBSYSTEM linker switch was used to specify the target subsystem at compile time, enabling applications to be compiled for different environments such as console applications, EFI boot environments, or native system processes. In this nomenclature, WSL follows the original naming conventions (although SUA should have been called WSUA).
    - jraph 1y ago
      Watch out. You are explaining serious stuff under a comment that was essentially "watch out, your parent comment was sarcasm".