Wayland misconceptions debunked
&gt; Wayland doesn’t support Nvidia!<p>There is a very high likelihood that when a user complains about Wayland support for Nvidia they mean this:<p>* user already assumes Nvidia is a bad Linux actor<p>* user knows Nvidia only supports buggy blobs<p>* user may even know Nvidia is bad to people trying to unblob the blobs<p>* user already went through the trouble of doing what it takes to get the bad Linux Nvidia blobs to work to play games on their machines<p>* user notices that the bad buggy Linux Nvidia blobs fail to work <i>at all</i> with Wayland<p>* user is understandably <i>even more frustrated</i> than they were before. So they ask you-- a Wayland person-- how can it be <i>even worse</i> for them now when they&#x27;ve already been generating much more complex and power-hungry graphics with their buggy blob than they&#x27;d ever do with Wayland.<p>If you&#x27;re representing Wayland, this problem is your problem whether you want it or not. Perhaps the answer is to make the protocol worse so the the Nvidia user doesn&#x27;t remain eternally maximally frustrated. Perhaps the answer is that isn&#x27;t possible and you&#x27;re stuck in the same boat as the user. Perhaps it means you start a hunger strike or gather thousands of devs to protest outside Nvidia&#x27;s headquarters until they improve. I have no idea.<p>But <i>please</i> don&#x27;t do that FLOSS thing where all the devs on a project teach each other to sync on, &quot;Sorry Mario, but your princess is in another castle.&quot; That pattern becomes it&#x27;s own problem and can quickly end up discouraging development even from potential devs who don&#x27;t care at all about Nvidia support.<p>&gt; Wayland doesn’t support screenshots&#x2F;capture!<p>What is the current UX for screenshotting, screencapture, and screencapture with audio for the most featureful DE that uses Wayland atm? Is there a program out there that offers push-button access for these three features (choosing the most sensible default format in each case)?