Certainly WSL2 integration has some benefits, but I'm not really using any of them at this point. My Windows terminal sshs to the Linux VM, my VSCode terminal opens in the Linux VM and everything feels fine. That covers my development requirements pretty well and rest of the stuff I do with native Windows tools (and I rarely need to cross-access files).
Never bothered to look for that. Can you link to it?
https://dev.to/bowmanjd/install-fedora-on-windows-subsystem-...
Not sure WSL2 will like Wayland. It seems better adapted to text-mode command-line Linux work (I'm aware it can run graphical apps). What I'd suggest is to deploy a new Fedora/CentOS WSL VM and copy your home into it.
> I used VirtualBox when I was first trying out Ubuntu
Oh yes. Unless it's a really nice machine and the hypervisor allows the VM to bypass hardware emulation when possible and use some form of virtio-like thing, it'll never be as fluid and snappy as when it's deployed on metal.
I don’t like WSL much. It feels like a second class environment, where the Linux filesystem is accessible via a network share.
In any case, it works. Windows Terminal is good enough, but I find Windows a hopelessly confusing OS with lots of places where it seems unfinished.
Considered all its pain points, I’d go with a VM under VirtualBox or VMWare Workstation. You’ll get a desktop-like experience if you go full screen and you still can get to the filesystem via the VM’s host drive plumbing. And nothing prevents you from running Windows Terminal and ssh’ing into the proper VM.