Hacker News new | past | comments | ask | show | jobs | submit login

The integration is very impressive, latest builds even have access to the WSL2 file system from Windows.

Starting up VS Code on a machine with WSL2 immediately gives you the option to use it as the VS Code environment, it is pretty great.




Integration is even tighter now its not just a VM like many commented here.


Can you write a single feature that's available in WSL 2 but not in VirtualBox?


I don't use virtualbox, so I'm guessing at some features:

* The Linux filesystem shows up in Windows as a disk even when the underlying VM is not booted, you can see an example here: https://redmondmag.com/articles/2020/04/08/~/media/ECG/redmo...

* And for me the nice one is the integration with VS Code, I just select which distro I want to work in and VS Code will start it (if it isn't running), connect to it as a remote dev environment, and be able to control it as if the VM were within VS Code. It can be done manually with VirtualBox, but VirtualBox gives me no advantages in return.

* The networking implementation makes both 127.0.0.1 which is occasionally useful for me.


Starts in one second.


That's not a feature. And in practice it's not even relevant, because you can start your VM at Windows startup and use Putty to ssh into booted system which takes a fraction of second.

Also slim CentOS image boots, well, not in one second, but something like 5 seconds. Fast enough IMO.


- seamless file system integration - network (you can use 127.0.0.1 to access services in WSL2 or Windows) i.e. it runs on the same home IP.




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

Search: