I don't think so, GNOME and KDE have never had the goal of making a reusable and generic compositor library like wlroots. >I'm actually more concerned about the fact that wlroots has/had to duplicate work done by Gnome and KDE With wayland, tough luck, the most you can get is a better editor/annotation tool.
In X, if you don't like Gnome's screenshto tool, you have a handful of other options. And a tool like flameshot becomes awkward if the compositor opens it's own dialog. So on wlroots, currently, an app can only get a full screen screenshot. Yeah, the problem is that each compositor has to implement it's own screenshot dialog, and you _have_ to go through that dialog for that compositor. Unfortunately the wlr portal is still not done yet and doesn't implement this. What's supposed to happen is that the portal daemon (NOT the application) pops up a dialog asking the user to choose which one they want. I'm actually more concerned about the fact that wlroots has/had to duplicate work done by Gnome and KDE (wlroots is more recent than much of gnome and kde's wayland support). If those projects want to create extra work for themselves, that's on them. > I am not sure how this is relevant if you're trying to write your own compositor. I also use X forwarding pretty extensively, but I'm probably a small minority these days.
I'm definitely not looking forward to reworking my entire workflow for minor benefits although I suppose I'll have to one day. I remember being fairly optimistic when I first heard about Wayland and Mir, the prospect of ditching X11 was enticing.īut now? I haven't really had to wrestle with X in a long time. Xorg was sometimes a bit of a pig too resource-wise, but that's when I was running a PC with 256MB of RAM.
In the specific case of Xorg I find the situation strange because I'd gladly have made the switch 15 years ago back when messing with nf was a common occurrence for me and it kept getting in the way (although a big portion of the blame was with the proprietary drivers, especially AMD's). People who were dealing just fine with previous solutions then start complaining about breaking things for the sake of breaking things and not being able to do things the way they were used to. Same reason systemd exists, the previous solutions were old and clunky and some people got fed up and decided to update.