WSL may be fine for a Windows user to get some access to Linux, however for me it misses the vast majority of what I value in a desktop distribution
-Better Window managers. This is subjective, but with Windows you are stuck with Microsoft implementation, and if you might like a tiling window manager, or Plasma workspaces better, well you need to run something other than Windows or OSX.
-Better networking. I can do all kinds of stuff with networking. Niche relative to most folks, but the Windows networking stack is awfully inflexible and frustrating after doing a lot of complex networking tasks in Linux
-More understanding and control over the “background” pieces. With Windows doing nothing a lot is happening and it’s not really clear what is happening where. With Linux, it can be daunting like Windows, but the pieces can be inspected more easily and things are more obvious.
-Easier “repair”. If Windows can’t fix itself, then it’s really hard to recover from a lot of scenarios. Generally speaking a Linux system has to be pretty far gone
-Easier license wrangling. Am I allowed to run another copy of Windows? Can I run a VM of it or does it have to be baremetal? Is it tied to the system I bought with it preloaded, or is it bound to my microsoft account? With most Linux distributions, this is a lot easier, the answer is “sure you can run it”.
-Better package management. If I use flatpak, dnf, apt, zypper, or snap, I can pretty much find any software I want to run and by virtue of installing in that way, it also gets updated. Microsoft has added winget, which is a step in the right direction, but the default ‘update’ flow for a lazy user still ignores all winget content, and many applications ignore all that and push their own self-updater, which is maddening.
The biggest concern, like this thread has, is that WSL sets the tone for “ok, you have enough Linux to do what you need from the comfort of the ‘obviously’ better Microsoft ecosystem” and causes people to not consider actually trying it for real.
Of course the problem is that wingetui isn’t there by default, isn’t integrated to Windows Update, no matter what, WinGetUI basically becomes yet another tray icon, alongside a half dozen other auto-updater tray icons that various vendors added since there’s no integrated facility to rely upon.
So sure, it’s a bandaid on winget, but it’s still awkward and the ecosystem is a mess. Compared to Linux where a distribution will have, in the box, an extensible central update facility maybe serving two different types of repositories (e.g. apt and snap, or dnf and flatpak).
well about networking: windows proxy settings just work transparently, while on linux it’s just a config option that applications may or may not respect (vpn still works perfectly, but not proxy)
True, though I’m mostly invested in the kernel networking behaviors, rather than having a nicely standardized place for proxy settings so that applications have a logical place to go.
It’s a fair criticism that in userspace, proxy settings have been not standardized and also TLS certificates are similarly a bit messy.
WSL may be fine for a Windows user to get some access to Linux, however for me it misses the vast majority of what I value in a desktop distribution -Better Window managers. This is subjective, but with Windows you are stuck with Microsoft implementation, and if you might like a tiling window manager, or Plasma workspaces better, well you need to run something other than Windows or OSX.
-Better networking. I can do all kinds of stuff with networking. Niche relative to most folks, but the Windows networking stack is awfully inflexible and frustrating after doing a lot of complex networking tasks in Linux
-More understanding and control over the “background” pieces. With Windows doing nothing a lot is happening and it’s not really clear what is happening where. With Linux, it can be daunting like Windows, but the pieces can be inspected more easily and things are more obvious.
-Easier “repair”. If Windows can’t fix itself, then it’s really hard to recover from a lot of scenarios. Generally speaking a Linux system has to be pretty far gone
-Easier license wrangling. Am I allowed to run another copy of Windows? Can I run a VM of it or does it have to be baremetal? Is it tied to the system I bought with it preloaded, or is it bound to my microsoft account? With most Linux distributions, this is a lot easier, the answer is “sure you can run it”.
-Better package management. If I use flatpak, dnf, apt, zypper, or snap, I can pretty much find any software I want to run and by virtue of installing in that way, it also gets updated. Microsoft has added winget, which is a step in the right direction, but the default ‘update’ flow for a lazy user still ignores all winget content, and many applications ignore all that and push their own self-updater, which is maddening.
The biggest concern, like this thread has, is that WSL sets the tone for “ok, you have enough Linux to do what you need from the comfort of the ‘obviously’ better Microsoft ecosystem” and causes people to not consider actually trying it for real.
Just in case a Windows user sees this, install WingetUI and your update flow will be fixed.
Of course the problem is that wingetui isn’t there by default, isn’t integrated to Windows Update, no matter what, WinGetUI basically becomes yet another tray icon, alongside a half dozen other auto-updater tray icons that various vendors added since there’s no integrated facility to rely upon.
So sure, it’s a bandaid on winget, but it’s still awkward and the ecosystem is a mess. Compared to Linux where a distribution will have, in the box, an extensible central update facility maybe serving two different types of repositories (e.g. apt and snap, or dnf and flatpak).
well about networking: windows proxy settings just work transparently, while on linux it’s just a config option that applications may or may not respect (vpn still works perfectly, but not proxy)
True, though I’m mostly invested in the kernel networking behaviors, rather than having a nicely standardized place for proxy settings so that applications have a logical place to go.
It’s a fair criticism that in userspace, proxy settings have been not standardized and also TLS certificates are similarly a bit messy.