3 ms·
There were 3 major pain points for me: * USB access is more difficult than just plugging something in. * Debugging tools like perf, RR, etc were either unsupp
by AlotOfReading 4y ago
There were 3 major pain points for me:
* USB access is more difficult than just plugging something in.
* Debugging tools like perf, RR, etc were either unsupported because they needed hardware counters or required custom builds (no system headers in apt to help either).
* The VM takes a lot of disk space.
The rest of the experience was fairly smooth. WSL2 can access the entire filesystem through /mnt/<drive letter>/. Windows -> WSL is a bit janky, but it works. GPU access is supported. Network access works. You can use a remote X session to get GUIs working, though you need to be comfortable with linux. Unfortunately having DISPLAY set caused pip to hang for long periods due to [1], but apparently that's been resolved.
All in all, it mostly replaced my windows usage by the end. It's also a great workaround for legacy IT environments where the system is configured with Windows and only Windows.
[1] https://github.com/jaraco/keyring/issues/531 https://github.com/jaraco/keyring/issues/531