This was refreshing to read. From a user standpoint the author echos my experience. I fired up a very recent distro (Fedora 38 I believe) that shipped Wayland a

This was refreshing to read. From a user standpoint the author echos my experience. I fired up a very recent distro (Fedora 38 I believe) that shipped Wayland as the default and immediately found dealbreakers: 1. Screen sharing from a web browser (Google Meet) required a multi-step approval process. It seems like first Wayland (or something) makes me choose/approve what I want to share and only then do I get to make the same choice within the browser. Very odd, confusing, overwrought. I'm actually surprised I don't see this complaint more often. 2. Flameshot (which is a godsend for taking screenshots quickly and mocking them up) was comically broken, especially in multi-monitor. They have a 'Wayland issues' page but it doesn't capture the full scope of issues that people report via Github issues. Reading this article you can see tell that the job of fixing Flameshot for not just Wayland but for every different compositor is just not something they are going to prioritize. 3. In my Chromium-based browsers I had to find and change an obscure key in ://flags to make them use Wayland correctly otherwise they would consume massive amounts of CPU.