A considerable amount of people assume Wayland isn’t particularly suitable for gaming, usually because you can’t turn off the compositor. This post will challenge that assumption and see how the current state of gaming on Wayland is, with a focus on KWin, KDEs compositor.
A very in-depth look at how Wayland works for gaming – from input lag to rendering – compared to X, including latency benchmarks.
One of the best things Microsoft did was invest early in technical writers who produced fantastic API documentation and books. Since Microsoft sacked them all and turned their “F1” help systems to junk and sacked all their quality assurance people things are not as they used to be. Linux documentation is usually terrible and the material I’ve seen so far on Wayland is mostly an in-crowd with a history talking among themselves which hasn’t been very accessible. This explanation while not the easiest or best read and not making enough use of diagrams is the kind of direction I think things should go in.
Better documentation helps give people an easier introduction and also helps transferable knowledge kick in easier which also helps encourage discussion as well as giving journalists and pundits something to talk about. That’s one of the key advantages of good documentation and books and in turn provides a better entry point to build something educational on top of and adds to positive marketing.
Microsoft and Apple and Google et al get loads of free marketing which they don’t always deserve in part because documentation makes it easy. Another thing which gets them undeserved free marketing is adding features or tweaking which can lead into hype for the sake of hype and marketing dictating the direction of travel which is not always a good thing.
Isn’t trying to get more video performance on the machine that is running the software (game) the whole point of Wayland?
If it couldn’t at least do that better then just bin it now, sunk cost be damned.