@kyle_pegasus@scalie.club @soc@chaos.social @zzt@mas.to @rootwyrm@weird.autos
Oh, well no I can imagine that'd be difficult, with X11 being the default assumption for so long, you wouldnt have built up robust abstractions to decouple your code. I work on a large legacy codebase for my dayjob atm. Of course I understand the manpower. You have to do shit slowly piece by piece, and that takes months even with several full-time devs.

I thought you meant *from scratch*. I even basically outright asked that? You almost sounded like making a wayland compositor was a fools' errand compared to a X11 DE. I was wondering if there was s(mething I missedx

As for screen capture protocols, we do have those finally: https://www.phoronix.com/news/Wayland-Merges-Screen-Capture

Using Niri, I've never had screen cast issues. And I think the latest they had to put more effort into was to do with pipewire streams (yes pipewire is now used for video too; i had no idea) so that webrtc support with browsers could work better.

Yes this is non-trivial stuff, but a lot of *is* implemented in smithay, for instance (example: https://smithay.github.io/smithay/smithay/wayland/image_capture_source/index.html)

And wlroots is actually the one that pioneered the early version of these protocols. Any compositor based on either would have to reimplement everything.

Global hotkeys are really one of the last things I find really annoying. They work fine on Plasma, though, from what I recall.