One word: asynchronous reprojection. Actually, that's two words.
At the moment, Linux VR users with SteamVR-native headsets like the Vive or the Index have a pretty similar experience to Windows users, but that's not the case for people using Oculus/Meta headsets. I use ALVR to connect my Quest 3 to my PC and it works great, I can play all my games and have a good time, but ALVR doesn't support asynchronous reprojection. I believe Virtual Desktop and WiVRn don't support reprojection on Linux either, but please correct me if they do since my entire point is moot then.
Asynchronous reprojection is a technology that lets the driver extrapolate what the next frame could look like based on the previous frame(s), essentially doubling your FPS if the game dips below your headset's refresh rate. It's a kind of frame generation, though specifically tuned for VR. It's very handy for preventing motion sickness as it stops everything going choppy and blech if your FPS drops. I play a lot of ETS2 & ATS which are currently not super well optimised in that framerate dips are common in dense areas even on high end hardware. The game runs great most of the time, but unless you have super overkill hardware (which is not achievable when running in VR), you will get frame drops in big interchanges or busy parts of some cities.
The Frame is a headset with a similar feature list/form factor/UX to a Quest, but will be SteamVR-native, meaning it will have reprojection! No longer will my 4090 occasionally produce results that make me want to hurl, even on low graphics settings!
Bring on the Frame! I look forward to my frames being buttery smooth once again :)