3 ms·
And this transition is nowhere near done. Just look at Kicad and pretty much any DAW that loads audio plugins (to name two major usecases where Wayland simply d
by drmr 1mo ago
And this transition is nowhere near done. Just look at Kicad and pretty much any DAW that loads audio plugins (to name two major usecases where Wayland simply doesn't cut it).
Sure Xwayland exists and mostly (not entirely) works, but that's a band-aid for what is essentially a "we broke it and don't care" approach.
- wing-_-nuts 1mo agoAlso, as benchmarks show, xwayland introduces pretty bad latency..
- dralley 1mo agoThe latency isn't that bad, it's reasonable for a compatibility shim.
- wing-_-nuts 1mo agoI can't find the benchmarks now, but the ones I recently saw on hacker news, xwayland was notably worse than either wayland native or xorg native. Bad enough to be noticeable by the average user.
- account42 1mo agoIt may be reasonable when you emulate a completely different platform but not when your are providing a compatibility feature in a supposed successor platform that can be designed to support that use case.
- Blackthorn 1mo agoThe daw problem is really really bad too. We've got a de facto standard forming right now where you link libwayland.so and hope the structs never ever ever change in the next 30 years.