I don't do anything like USB pass through. I use it purely for the linux tooling to support software development. I find it a perfectly suitable system for that purpose and would recommend it.
Not available in Win10 until recently, and broken and fixed even more recently... but thank you for the heads up. It seems this is finally a thing.
I will have to see if it actually works in my case. The devices are intolerant of timing. Even using usb-serial instead of legacy hardware, let alone the ip stack, can be a problem unless using real ftdi adapters.
Basically virtualizing rs-232's hardware flow control into usb packets was always technically invalid since the beginning, but if the host is overwhelmingly fast enough, you get away with it, usually, and by now all new serial devices have adapted to expect the behavior of usb-serial adapters since that's what everyone has. For that reason, new devices generally tolerate even worse timing and you can even get away with going over ip. But the fact is the timing is garbage by that point and not everything works.
Still, I'm sure it's working well enough for most things or else there would be more reports that it doesn't work.
Since WSL2 is basically VM now, i guess we can passthrough the usb device to VM and skip the whole IP stack, latency is still there, but much better than usbipd
It was possible under wsl1, but wsl1 is an entirely different thing.
"never had any issues" is a meaningless statement. I "never had any issues" with infinite things I never tried to do in the first place.