Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> You can use WSL but file access is dog slow

You can also use WSL2, which has fast file I/O. Unless you're trying to write to files in /mnt/c, at which point the comparison makes less sense, and a more accurate comparison would be trying to write to files on a remote Windows machine from Linux (also slow).

> compared to the real thing

Um, it is the "real thing". It's running in a hypervisor, on the real CPU core.



WSL2 is just a VM. It's nothing new. WSL was actually an interesting concept but it couldn't be implemented right sadly.


How is running in a VM, on modern hardware with virtualization supported natively by the CPU, not the "real thing"?


There's no transparent support for anything GUI or GPU related. There's no ability to use another hypervisor without rebooting the machine and changing a flag and then changing it back. There's no seamless access to the same filesystem. There's no seamless networking. There's no interprogram communication across the OSes without the (kinda broken) network.


Only the first one is something you get running Linux on bare hardware. The rest are goalpost-moving (and I don't even know what we'd be discussing to make those valid points honestly). And about GUI/GPU, that's actually not a valid point either, as WSL2 has OpenGL support now.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: