Are We Wayland Yet?
From what I&#x27;ve read, it seems like Wayland&#x27;s &quot;controversial design choices&quot; don&#x27;t stem from developers being inconsiderate of different workflows, but rather from the intention of making a general purpose protocol.<p>Being general purpose means that things like screenshotting capabilities are not the protocol&#x27;s concern and should be implemented in the upper layer(s) instead.<p>In that case, this general purpose approach seems to me like the right way to tackle the problem, since we won&#x27;t need a different protocol for use cases that fall outside the traditional desktop paradigm. You can just use Wayland and implement your own business code on top. There&#x27;ll be a de-facto standard way to do graphics on Linux, no matter your use case.<p>Correct me if I&#x27;m wrong about this. I&#x27;m not a Wayland expert (I have many articles and books in my to-read list).<p>I&#x27;m excited about Wayland for the simple reason that I hate screen tearing.