Remix.run Logo
petterroea 2 hours ago

I, for one, have had to explain to Juniors multiple times that WSL isn't Linux, and why it's no replacement for Linux. Happens almost every time they try to do anything more advanced than a WSL hello world, and it inevitably fails.

I still let them try, because it beats me having to check "is wsl good now", and they learn much better from personal experience than someone more senior who uses arch btw just telling them "don't use windows"

StableAlkyne 2 hours ago | parent | next [-]

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 2 hours ago | parent [-]

Mostly its related to filesystem and permissions. Interface between windows and Linux, and mismatch in how the two work.

Compute etc is fine!

yread 2 hours ago | parent [-]

Yeah its best to avoid using the windows filesystem for anything else but a source of cp -r

bezier-curve 2 hours ago | parent | prev | next [-]

WSL1 is not Linux because it is mapping system calls from the Linux kernel ABI to NT. That sounds like what you're describing. WSL2 is a Microsoft distro running in a VM that integrates into Windows.

I use WSL2 every day and it has some annoying quirks with how their Wayland implementation behaves with DWM, but otherwise it's just a Linux environment.

DeathArrow 2 hours ago | parent | prev [-]

Actually, WSL is pretty good for development. Of course, I wouldn't use WSL to run server software.