wayland
The problem with Wayland is really not the protocol itself, nor that it is extension-based (that is actually a very good thing!), nor some weird conspiracy theory about it 'competing' with Xorg or being some kind of 'takeover' (it's the same people developing it! It's effectively just the next version.)
The real, actual problem with Wayland is that some desktop environments started defaulting to its use before it and its ecosystem were at feature parity with the systems and tools people were already using. Some projects jumped the shark. That's it.
We can be critical of something like Wayland without losing all nuance and inventing conspiracies and doom that don't actually exist.
re: wayland
@joepie91 that seems more like a problem with the desktop environment devs not being patient. I was quite stubborn about using Xorg until relatively recently because of how desktop environments jumped the shark, exactly as you said. I assumed until recently that it was still not particularly usable and I was pleasantly surprised.
re: wayland
@ch0ccyra1n @joepie91 i had the opposite experience
everyone told me how great wayland is and that i shouldn't use x
i switched to wayland and i am fighting with wayland issues on a daily basis and my gosh i dont have the spoons to fix everything but also not to switch back
so now i have a half baked broken setup that i'm daily driving :,)
re: wayland
@schrottkatze @ch0ccyra1n What specific issues are you running into today, and on which DE? As there's a fairly good chance that they are DE issues rather than Wayland issues, by this point (with the important stuff being more or less stable now).
re: wayland
@joepie91 @ch0ccyra1n sway
can't find any half decent status bars (used to use polybar and waybar is a PITA)
wofi is cursed too and it's all just a meh ux
yes ik it's bc i havent' properly set up a lot of stuff, but still
i now need to look for a new statusbar (which is exhausting) and aaa ><
the standards for wayland apps seem to somehow be even lower then for x apps and that's really depressing.
also, no oneko :(
re: wayland
@schrottkatze @ch0ccyra1n Right, it looks like all of these don't work because they expect some sort of privileged access to the window manager (in the sense of being able to manage windows/layering and/or capture input)?
That's definitely one of the major items that still seems to be missing standardization - KDE has a custom extension (org_kde_plasma_shell) but only KWin implements that, and I can't immediately find a standardized equivalent :(
This is essentially the "no standard protocol for separating window manager from compositor" problem, as far as I can tell. Which is solvable in principle, but it doesn't seem like anyone has yet.
