yep, compositor latency is infuriating when you're used to non-composited UI

Can you really tell the difference? What's the latency? Are your eyes that sensitive?

I think our sight is all a little different. I can clearly see 50/60hz strobing in light when others can't. Back in the old CRT days I would get strained eye sight and nausea if I worked at monitors running below 85hz, unless it had long lasting phosphors like the old monochrome CRTs.

Good LCDs are static unless you're running a dvi-vga-displayport-vga-hdmi dongle monster where the pixels are inevitably shifting a bit every instant. What you're more likely to be seeing is PWM backlight flickering at you.

If it's indeed the LCD and not the backlight, pray tell us the model so we don't end up buying it.

They didn’t say anything about LCDs.

I dont have this problem with LCDs...

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.

That's no reason to add another layer of avoidable compositing.

You'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.

Which Wayland compositor allows me to exclusively use front buffer rendering without vsync?

KDE seems to have a flag to turn of the compositor, which seems to result in no tearing.

Nvidia stereo 3d only works if the compositor is disabled in Xorg.

Wrong: https://www.gamingonlinux.com/articles/gnomes-mutter-gets-fu...

I get it, all these features that used to just be supported by the one Xorg server now need to be supported by individual compositors - but still, it is simply misinformation that "Wayland" is broken because Mutter / Kwin / Sway are incomplete.

How is a 1yo merge request about "surface fullscreen unredirect" relevant to a complaint about forcing compositing on WINDOWED applications?

If it isn’t broken, then give an example of a compositor that isn’t broken.

A protocol with zero practical implementations is, in practice, broken.

I specifically said "windowed applications". This is talking about fullscreen applications.