To be clear I meant the experience is fine when running on a 100ms link. I haven't measured the actual latency. That said it uses QUIC and sends the data as tiles, which are displayed immediately, so I suspect it is basically as low latency as possible. It does lead to fun mosaic style tearing which half of me finds cool and half wishes it didn't do that, but side-by-side with Xpra it's much faster and less annoying than waiting for a whole frame which is what Xpra does.

I'm running an old Qt X11 app with a modern retina MacBook with multiple different density screens and it works fine. There were some minor issues with that to start with but I pretty much just said "this happens, please fix it" and Claude figured it out without even having access to a Mac, which is impressive.

Honestly the thing that was hardest was keyboard layout. That kind of stuff never worked well for me in any remote desktop app, and now I can see why! You might never notice if you only use the US layout tbf. It works pretty well now though - I got it to query your local layout and the dynamically build an X keyboard layout and send it to the server.

I've run it with up to about 4 large windows and it seems to work fine. It doesn't send anything when nothing is changing so lots of windows won't matter unless they're playing videos or whatever - it's more designed for old Windows/Qt/Gtk style apps. I suspect you could do better with a traditional video codec but unfortunately the server I use has no GPU so that wasn't really an option.