No. Essential features depend on the "compositor" because Wayland doesn't support them. You're mixing up interface and implementation.
But the reason for that misconception is presumably that what most users would customise with X was replacing the WM - there was little demand for lots of different X servers other than for very specific needs or different platforms.
Meanwhile with Wayland, we need a compositor to replace every X wm people still care about.
For me, that's the big blocker - as long as there's no drop-in replacement for bspwm, it's a hassle for me to move over and none of the "benefits" of Wayland matter to me.
(EDIT: In fact, because of how Wayland shifts responsibilities, Wayland has led to more code being shared between compositors via projects like wlroots because the burden to implement a Wayland compositor is far higher than to implement a window manager for X, and more people care about window management functionality than the low level server functionality; eventually I believe and hope we'll end up with a couple of dominant compositors with a common set of extensions supported for all the "missing" X functionality, including a wm extension, and we'll be back at pretty much parity with X)
I'm not excited. There's no reason we should need dozens of compositors that are mostly identical apart from code that could easily live in a separate process.
That wlroots is getting better at making it easier to build a compositor is a poor bandaid from just removing the need to build a compositor at all.
It's one of many examples of Wayland throwing the baby out with the bath water.
As Wayland is just a protocol itself, the client doesn’t care how it’s implemented. Thus I see Wayland providing the extreme flexibility to implement its protocols how you see fit. Right now wlroots makes it easiest but if in a few years another implementation proves to be better, all those client programs aren’t going to stop working. For now the scene graph allows a whole bunch of compositors/window managers to be easily written that replace x11 ones. And better designs can be further iterated.
Until there is a compositor offering the same ease, either a bunch of WM's people use and care about won't get an equivalent for Wayland, or it will take a lot more time and effort.
As it is, for example, I'm not moving to Wayland before there's a drop-in replacement for bspwm. River seems to be close-ish to being able to offer something like that, but the benefits of Wayland do not really matter to me and so I have no interest in investing time in replacing bspwm for minimal gain.
> As Wayland is just a protocol itself, the client doesn’t care how it’s implemented. Thus I see Wayland providing the extreme flexibility to implement its protocols how you see fit.
This is true for X11 as well. X11 is just a protocol. But in practice we ended up with a small set of implementations exactly because the pain of implementation was too high, and even most separate servers (e.g. Xephyr for example, or, in fact Xwayland) were often based on Xorg the way many Wayland compositors are based on wlroots.
But that is with the APIs allowing out of process WMs. For Wayland the lack of a WM protocol means you can't avoid a higher proliferation of compositors until someone adds such an API, and it'll hold back development by making a lot of people spend time duplicating compositor code for no good reason.
> For now the scene graph allows a whole bunch of compositors/window managers to be easily written that replace x11 ones. And better designs can be further iterated.
It's great that it's getting easier, but the point is this is the "wrong order" - if you have even a fairly basic WM API very few WMs will care about the scene graph at all. It's like people are intent on ignoring the lessons of what actually worked well with X.
It's really not my problem - I'll stay on Xorg until Wayland is more suitable, however many years that might take. But anyone who cares about Wayland ought to take seriously that the proliferation of compositors will become a nightmare, whether or not more and more of them depend on wlroots, as it means more and more packages to rebuild, test and distribute whenever there are wlroot fixes, for example, for very little gain vs. simply moving the bits that will differ between wm's out of process.
I would like to know more about that. Have you some resources that demonstrate that?
> Depending on the compositor of course.
Which one do you use?
on Gnome 41
Which leads to a big misconception that many users have, even here on Hackernews.
"Wayland doesn't support Y" or "Z doesn't work on Wayland" statements only make very limited sense.
Wayland is just a protocol. Unlike X, there is no shared codebase that is used by all implementations - aka compositors.
There are several important compositors, all with their own individual quirks. Which is part of the problem...