3 ms·

Yeah I don't understand the love for WSL. Within the first couple weeks of using it, I've run into * Time doesn't stay in sync after sleeping, which breaks pac

Yeah I don't understand the love for WSL. Within the first couple weeks of using it, I've run into * Time doesn't stay in sync after sleeping, which breaks package updating. * It doesn't get the DNS servers it should from DHCP, so you have to go manually edit /etc/resolv.conf * The filesystem is super slow, and git commands take multiple seconds. All stuff that can be worked around, but I don't have to deal with this crap when just running Linux, and all Windows gets me is a clunky UI and ads. It's mystifying to me that everyone is somehow capable of managing fleets of Linux servers just fine, but for some reason managing developer Linux workstations is impossible, so we end up with these Rube Goldberg machines.

NikkiA 3y ago
The problem I see most often is that WSL causes processor stalls in my other VMs, I'm not sure if it's intentional to force you to use WSL or the Hyper-V VM subsystem exclusively, if it is I can't see how it's a wise move. Enabling Hyper-V also meant that virtualbox completely lost the ability to have a clock that ran properly - each VM was seeing the hardware timer out by 3 seconds every minute, and thus the only fix there was to run ntp every minute. vmware wasn't affected somehow.
lenova 3y ago
> The filesystem is super slow, and git commands take multiple seconds. Ugh, this is a known issue in WSL if you try to use git on the host operating system (/mnt/c/Users/path/to/repo)... there are cross-system file system virtualization issues in WSL2 when reading from the Windows hosts. Workaround is to have your git repos within WSL itself (~/my-git-repo) to have native performance.
- capableweb 3y ago
  All of these workarounds unfortunately adds up, and after a while it's just too much to having to deal with, when you could have just gone straight up for a Linux/Windows dual boot setup and not having to deal with any of those issues at all.

NikkiA 3y ago

The problem I see most often is that WSL causes processor stalls in my other VMs, I'm not sure if it's intentional to force you to use WSL or the Hyper-V VM subsystem exclusively, if it is I can't see how it's a wise move. Enabling Hyper-V also meant that virtualbox completely lost the ability to have a clock that ran properly - each VM was seeing the hardware timer out by 3 seconds every minute, and thus the only fix there was to run ntp every minute. vmware wasn't affected somehow.

lenova 3y ago

> The filesystem is super slow, and git commands take multiple seconds. Ugh, this is a known issue in WSL if you try to use git on the host operating system (/mnt/c/Users/path/to/repo)... there are cross-system file system virtualization issues in WSL2 when reading from the Windows hosts. Workaround is to have your git repos within WSL itself (~/my-git-repo) to have native performance.

capableweb 3y ago
All of these workarounds unfortunately adds up, and after a while it's just too much to having to deal with, when you could have just gone straight up for a Linux/Windows dual boot setup and not having to deal with any of those issues at all.