It is :) But wsl2 is a bit more than X (or Xwayland or whatever it is). - It let's you go out of that "userland only" view that WSL1 has. So you can actually m

It is :) But wsl2 is a bit more than X (or Xwayland or whatever it is). - It let's you go out of that "userland only" view that WSL1 has. So you can actually make ICMP calls and use traceroute/mtr form it and so on. You can see actual load of that WSL2 (wsl1 has a ... hardcoded load info :D) - You can safely have write access to a filesystem in both directions. Also write from windows to WSL2. It's even integrated into explorer if you want. On WSL1 that usually ends up with broken filesystem (ask me how I know - tried twice...) - You can use regular services like initd/systemd. You can eaven run real docker deamon more or less like on a regular linux system - The integration from vscode is still superb - As the filesystem is NOT visible as a folder in c:\windows, crappy antimalware/DLP tools can't see what binaries you run. This means that most likely in a corporate environment it will run much much faster. If you worked in a company with underpowered DLP hardware you will know what I mean It does complicate a few things, like networking which can break when you use vpn's, but there are workarounds like wsl-vpnkit on github.