3 ms·
That's no reason to add another layer of avoidable compositing.
by mrob 6y ago
That'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?