Earlier quoted context omitted.
Depends a lot on what you are trying to accomplish. The inability to get something akin to VT220 terminal access and shell scripts on a POSIX-based system without resorting to a virtual machine (a la WSL2) is a deal-breaker for me. The steps for using scripting languages (e.g. Node, Python, Ruby) is typically entirely different on Windows than it is from all other server and desktop platforms. For those who can spend…
WSL2 is not a virtual machine, it's a subsystem . It's basically the opposite of WINE. You can run all of your favourite languages nearly identically to Linux on Windows either via Docker or WSL2. > Windows requires emulation to run aarch64-based containers. Except on Windows for ARM Making Windows and Linux the only platforms with ongoing support for both ARM and Intel CPUs, unlike MacOS where Intel support will eve…
"WSL 2 ... uses the latest and greatest in virtualization technology run a Linux kernel inside of a lightweight utility virtual machine (VM)."
https://learn.microsoft.com/en-us/windows/wsl/compare-versio...
WSL1 is not a VM design, but that design reached its limits.
A VM doesn't make it bad - I don't do a lot with WSL but I like it a lot. It's not slow or limited.