3 ms·
Interesting, I've been using it with zero issues (including performance) for several years now. Compiled stuff, ran scientific calculations, trained neural nets
by StableAlkyne 6mo ago
Interesting, I've been using it with zero issues (including performance) for several years now. Compiled stuff, ran scientific calculations, trained neural nets with GPU passthrough, even switched over a workload from an old Red hat box to WSL Alma.
Only weirdness has been systemd can sometimes be quirky, and GUI stuff can be glitchy (which doesn't affect me much, because 99% of what I do is in the terminal)
So, anecdotally it is perfectly adequate for workloads beyond a Hello World. What issues are you running into?
- petterroea 6mo agoMostly its related to filesystem and permissions. Interface between windows and Linux, and mismatch in how the two work. Compute etc is fine!
- yread 6mo agoYeah its best to avoid using the windows filesystem for anything else but a source of cp -r
- pjmlp 6mo agoHardly any different from mounting UNIX filesystems that don't obey exactly the same semantics.
- tracker1 6mo ago/mnt/c etc from within WSL, and access to Linux FS paths are effectively a plan-9 file share service... Beyond this, if you use Docker Desktop (or similar) with volumes on the host OS (Windows or Mac) it's a weird FS sync between the host and container environment)... if you do volumes in WSL2 inside a Linux/WSL environjment it works fine (normally). Permissions between Windows and Unix are always (generally) a mismatch, as is the nature of OS differences.