4 ms·
> I used to develop on Linux, but eventually wanted something that "just works" so I switched back to Windows. Much less time spent tinkering and more time spen
by ayushnix 5y ago
> I used to develop on Linux, but eventually wanted something that "just works" so I switched back to Windows. Much less time spent tinkering and more time spent getting things done
I started recommending WSL on Windows to a few friends who wanted to get a taste of how Linux works after hearing praises about it although I've never actually used it myself. I recently realized that systemd doesn't work on WSL (without ugly hacks) and /mnt also mounts Windows disks.
I have stopped recommending WSL since then. Although I don't recommend anyone to use Linux either.
- wongarsu 5y agoWSL works pretty well for typical command line usage (your typical "grep | sort | uniq" stuff) or for "this command line tool only runs/compiles on linux" usecases. If you push it much more than the abstraction starts getting leaky and you have to get more involved (though WSL2 can be pushed a lot more, e.g. getting systemd running in WSL2 doesn't seem that bad [1]). 1: https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950 https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee...
- kanetw 5y agosystemd doesn't work on WSL? Blessed Microsoft.