I updated my work computer today to be greeted with this:
You still need a CPU enabled for Virtualization and Windows Pro to use WSL, which are the same restrictions from Hyper-V. I’m very curious to see if this is capable of changing the workflow. I know nothing about WSL 2, but I have used the original WSL. At that time, you couldn’t use File Explorer to navigate the embedded linux filesystem, and any attempt to use the Ubuntu Terminal to play with files created by or stored on NTFS partitions would mess with the file’s permissions so hard to the point of being unusable or even removable to either system.
So perhaps I need to give WSL 2 a try, I see they got RHEL based flavours enabled now like Fedora. Maybe it’s time to give that another whirl.
A developer his entire adult life, Kyle spends his professional and free time finding new and interesting ways to solve the same boring problems (less he drive himself insane).
When not slinging code, he can be found being the happiest father and husband to the best little family ever!