3 ms·
All your stuff is already composited, and if done well it doesn't add much latency at all. You're still paying it in X, just badly, and with none of the upsides
by kllrnohj 6y ago
All your stuff is already composited, and if done well it doesn't add much latency at all.
You're still paying it in X, just badly, and with none of the upsides (eg, no tearing). Even if you're trying to avoid a compositor, none of the UI toolkits are participating in that nonsense.
- mrob 6y agoThat's no reason to add another layer of avoidable compositing.
- kllrnohj 6y agoYou're not. It's already there and already happening. The difference is just we all stop pretending anyone is doing anything else. As in, kill the terrible X vector crap, and add reliable compositing APIs so things like video playback in apps stops being so incredibly bad (see video in browsers sucking in linux and not anywhere else). You know, catch up to what literally everything else is doing. Windows, MacOS, iOS, Android, etc.. are all exclusively compositor-based window management systems. And they don't have latency issues, as ways to avoid what little latency compositing adds can be avoided in cases when necessary, like front buffer rendering extensions on Android for VR. Literally only X remains stuck in the 90s.
- mrob 6y agoWhich Wayland compositor allows me to exclusively use front buffer rendering without vsync?
- josefx 6y agoKDE seems to have a flag to turn of the compositor, which seems to result in no tearing.
- COGlory 6y agoNvidia stereo 3d only works if the compositor is disabled in Xorg.