3 ms·
Every system makes tradeoffs. If you find yourself continually fighting to get something to support your specific workflow, it is usually best to be open to adj
by underwater 4y ago
Every system makes tradeoffs. If you find yourself continually fighting to get something to support your specific workflow, it is usually best to be open to adjusting your workflow. Or swap to a different solution.
In my experience, WSL 2 with Node, Terminal and VSCode has felt like a first class experience. It's miles ahead of WSL 1, which was theoretically a great idea, but failed in practice.
- alexvoda 4y ago> It's miles ahead of WSL 1, which was theoretically a great idea, but failed in practice. Indeed. Do you know what technical factors made WSL1 undesirable in practice? Why were the disk performance issues insurmountable? Why was it so hard to maintain? The reverse, WINE, is arguably very successful.
- CoolCold 4y agoit's the common curse for emulators - Cygwin, Wine, WSL1 - subset of features of supported and not always right/can be done right. And you always chasing the origin with a lot of efforts. I highly doubt things like mounting filesystems ( I do run BTRFS for LXD in my WSL2 system) or other just-slightly-beyond-posix things would work reliably or at all with such kind of emulation that WSL1 do. In other words - it would never be Linux enough as native Linux (with VM type of WSL2). I.e. I still use both WSL1+WSL2, but WSL1 is basically a very small shim when I need some socat/grep/shell & where it needs to share networking with main system, while main work is much better in WSL2.