With all due respect: I don't have time. I just asked because this was an issue last time I tried sway, and I was curious about improvements since then. It was not meant to razz on your wm :)
As a maintainer and contributor to several projects I already use (and thus see the return on) I already see myself too short on resources to follow up everything I'd like to.
Trying to fix shortcomings in projects which (for me) are not yet production ready just doesn't make it onto my TODO list. I hope someone does help you fix this though.
Really. No harm meant. Hope it didn't come off that way.
That's fine, sticking with X is a totally acceptable option. If they _want_ to move to Wayland, though, and it's missing something they need, then of course they should help work on that thing.
Given that these issues has persisted for so long and that they seem solved in Gnome and KDE...
Not accusing you of full NIH, but are there any technical reasons for not just reusing/leveraging kwin or whatever Gnome uses, instead of creating your own compositor library where all these issues has to be solved, yet again?
kwin and Gnome's solutions aren't reusable on other compositors. Gnome is awful at making their stuff reusable. KDE is much better, but their clipboard stuff isn't reusable, and Sway's likely won't be either due to the nature of the problem. There are plans to collaborate more with KDE on reusing KDE components in Sway and other compositors, which both parties are excited about.
I've been using Wayland on Fedora 25 GNOME sessions for a few weeks now. I've not noticed any hiccups on copy/paste and I've definitely been doing it across Wayland-native and XWayland applications.
Sway works great as long as you have a system that can handle Wayland. I've been having terrible luck with NVidia hardware lately -- proprietary drivers are known not to support Wayland, and Wayland / Nouveau has been unstable with the hardware I use. But AMD and Intel systems are rock solid, and I've switched over to sway there.
> Wayland is just super nice compared to X11 for enough tasks to justify using it.
I'd like to hear what makes it better for you in terms of day-to-day experience. I can look at feature lists, but those often don't give a good picture of the reality that people experience. Given your enthusiasm for Wayland, I'd like to hear it!
Wayland is smoother, does not have graphical glitches and everything performs consistently.
Take this (slightly contrived) example: In Gnome 3 you can "zoom" out to panarama view all your running applications, while you have a HTML5 video running in your browser and everything just runs flawlessly, with almost no system-load, and no tearing or any nonsense. All this while you zoom in and out on whatever app or desktop or workspace you want to focus on.
A less contrived example: Vertically scrolling a document in your browser or whatever should never ever tear. Ever. On X11 it often does. On Wayland it doesn't.
My best simple comparison would be iOS vs Android. There's something about that extra little bit of responsiveness on iOS, that jerkyness you immediately notice on Android when you've gotten used to consistently smooth 60fps interfaces... That difference is something you feel.
After using Wayland for a while, you'll notice that feeling yourself on your desktop too.
Sounds like your graphics card isn't configured correctly, maybe?
I use X11 (StumpWM, actually) on three computers with different graphics cards and system configurations, and I don't have jerkyness, tearing while scrolling, or graphical glitches on any of them.
I'm using factory config on well supported Intel GPUs. I can see the difference pretty clearly. Especially when dragging a full-screen window playing youtube or whatever.
This works fine with Wayland. With X11 I get tearing. I'm pretty sure this is what everyone else is complaining about too.
>Take this (slightly contrived) example: In Gnome 3 you can "zoom" out to panarama view all your running applications, while you have a HTML5 video running in your browser and everything just runs flawlessly, with almost no system-load, and no tearing or any nonsense.
Same with a good compositing X11 window manager. In fact wayland does not dictate gpu accelerated rendering nor compositing. And there is much more to look at when talking about wayland vs X11, many details and a few major things.
But in general, no, wayland is still not ready. The people leading the desktop wayland parade have to all take a step back and think, while nvidia needs to agree with kernel people on how to manage memory. Then we can start thinking about replacing X (start, as there are still many more details).
These all sound like things that benefit heavyweight desktop environments and don't really impact tiling window managers at all.
I use DWM, no graphical glitches, no tearing, no jankiness, absolutely consistently quick (which actually kind of removes "smoothness" from the equation; everything is pretty much instantaneous).
Scrolling a document in Chromium very rarely pauses, but only ever when there's some bad JS blocking the UI, which isn't related to the window manager at all.
I want to use Wayland, but it breaks a few tools I use (Autokey [0], marathon [1]) as they depend on X-specific tooling/APIs (for marathon: wmctrl, xdotool). So I'm disabling Wayland for now even though I'd like to use it (for starters, simply to roll with GNOME's boat, since Wayland is the default on Arch).
--> Are there Wayland equivalents to wmctrl and xdotool? Any plans for them? If no, does Wayland provide a complete-enough API to write similar tools for Wayland?
Is Wayland actually that much nicer than X11? Like, I know the architecture and code and nicer, but as the end user, do you actually experience anything different?
Just in time for Fedora making Wayland the new default :)
Seriously though. Someone please make a good, working Wayland tiling WM.
Wayland is just super nice compared to X11 for enough tasks to justify using it.