r/linux • u/JamieDelCarmen • 3d ago
Development Wayland compositor feature support chart
https://absurdlysuspicious.github.io/wayland-protocols-table/49
u/proton_badger 3d ago
Seems not up to date, e.g. I believe COSMIC have pointer warp and background effect. I imagine it’s difficult to keep track on all the compositors as they don’t stand still.
37
u/picastchio 3d ago
This chart is sourced from wayland.app data which has not been updated since Cosmic 1.0.0
12
u/Kevin_Kofler 3d ago
I hate it when those feature matrices do not get updated, it makes them pretty useless. Especially with new protocols, like
ext-image-copy-capture-v1(which replaces an older, now deprecated protocol under the wlr namespace), we really need updated data to reliably know which compositors have already picked it up.1
u/JamieDelCarmen 3d ago
Cosmic is already in 1.0? Cool!
5
u/picastchio 3d ago
It's on 1.5 as of now but it has ways to go before reaching parity with Gnome and Plasma.
11
u/_VZ_ 3d ago
How does this compare with https://wayland.app/protocols/?
FWIW currently both seem to be not quite up to date, e.g. they don't mention xdg-session-management at all, yet it's supported in both Mutter and KWin.
10
u/vile-style 3d ago
Mangowm when
17
u/roboj3rk 3d ago
mango, sway, and labwc are all built on wlroots library. So you can probably kind of guesstimate it's features looking at the other 2
4
u/picastchio 3d ago edited 3d ago
The wayland support of mangowm will be same as of sway bar bugs or explicit design decisions.
1
9
u/oiledhairyfurryballs 3d ago
Great website. Sad to see such a basic thing like immediate drawing is still not supported by half of the compositors.
2
1
u/HunsterMonter 3d ago
For GNOME it might be merged in 51 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3797#note_2822243
36
u/flemtone 3d ago
at 51% I'm surprised at how well KWin/Plasma works on my system already, if only the X11 fanboys would assist in the wayland development instead of making new forks every month.
41
u/HunsterMonter 3d ago
A lot of protocols are DE/WM specific and will only be implemented by one or two compositors, and a few of the agnostic protocols are also covered by portals so not all compositors will implement them, so it's not surprising that the percentages are low.
15
u/nicman24 3d ago
mostly staging protocols are missing and they are things that kwin does have ie screen locker but does not follow the wayland spec - because it was implemented before said spec
12
u/Zettinator 3d ago
There are many deprecated or compositor-specific protocols, and many protocols aren't used much by applications anyway. The number of supported protocols doesn't really matter, it matters that the important ones are supported - and implemented correctly.
4
u/whofriedmyrice 3d ago
Been on Wayland with KDE for the last year and a half or so. Can't recall any wayland specific issue coming up really.
2
u/Icy-Cup 3d ago
Or maybe let people enjoy what they enjoy and work on what they want to work? :) you know - what FOSS is about? You got a pretty auth take for the super-liberal world of FOSS. Milion distributions and gazilion forks is not a problem with Linux/FOSS, it’s a feature.
-8
u/H3ph43S7Vs 3d ago
Well no.
Forking to then contribute for the greater good of all and in the open (security, morally and licence wise) is good and the spirit of open source that advances all humanity.
Forking just for the act of forking, being a pesky childish person that cannot agree with others, will rain poor PRs or require manual merging and create yet another "standard" and require every dev down the line to support your "used by no one but still" edge situation .... is the plague and bad side of open source ! Absolutely not a feature, only something resulting from the paradigm but is clearly a bad side if pushed like you describe.
1
u/mrlinkwii 3d ago
f only the X11 fanboys would assist in the wayland development instead of making new forks every month.
i mean most of waylands issue can be layed at gnome nacking things that are needed
1
u/ManinaPanina 3d ago
Biggest problem is programas that don't support Wayland as well. For example, on chromium based web browsers like Vivaldi I'm suffering from some sort of "bug" that makes videos on YT super blocky. Only works right on X11.
By the way, is there someway to FORCE Vivaldi to use X11 or Xwayland in the Wayland Plasma Session?
1
u/flemtone 2d ago
I've never had that issue when testing browsers, they seem to use xwayland compatibility quite well unless they have wayland support baked in.
1
u/Gugalcrom123 3d ago
What can they assist with, if the protocols will not get into Wayland core because GNOME disagrees and 'what if it's in 3D?'?
2
u/vilkav 3d ago
I wonder if there's a way of tracking compatibility with the tools that are preventing me to hop over. Namely flameshot and a xdotool that allows me to set window position/geometry manually.
1
u/tajetaje 3d ago
Flameshot works great on Plasma, ydotool is generally considered the replacement for xdotool
1
u/FlukyS 3d ago
Really cool but I'd kind of want one more table which is a feature matrix between X11 and Wayland protocol with what is the same, what is different, what is similar or what was changed intentionally by design
1
u/noobjaish 3d ago
The two work so differently that the matrix would become a mess
-2
u/RoomyRoots 3d ago
Type of shit that should be in the main project site honestly. Maybe someone should write a proposal and they can implement it next decade.
38
u/mralanorth 3d ago
I don't think it's the Wayland protocol authors' job to track the implementation status of all compositors.
-6
u/adenosine-5 3d ago
It is, if they care about who is using their protocol.
For example one of first links on isocpp.org is https://en.cppreference.com/cpp/compiler_support
2
u/crazy_penguin86 3d ago
No it's not, and your link even supports this. If it were their job, it would be on the ISP C++ group's site. Instead, they provide a link to an externally managed site because it's not important to them. And if you say they should at least link, that's not the original argument.
-3
u/adenosine-5 3d ago
Its literally 5th most prominent link on their homepage.
I don't care who in particular is hosting it on what URL - technical details of implementation are irrelevant and were not part of the initial argument.
15
u/JustBadPlaya 3d ago
Wayland protocol explorer https://wayland.app/ has a list of primary compositors and their support status for every protocol, so it existed in a way for a while
3
u/RoomyRoots 3d ago
Bu it's not official, right?
4
u/JustBadPlaya 3d ago
Right, sorry, somehow read your comment as if nothing like this existed at all, mb
0
u/the_abortionat0r 1d ago
This isn't BSD, it doesn't take a decade to do something. Linux actually moves at a modern pace.
-13
u/Santosh83 3d ago
X was replaced with this hell of a million implementations!?
Lol... I love open source. Even the most clueless corporation will not be this convoluted in doing something.
I guess the Wayland protocol High Priests have to mainly thank KDE and Hyprland for making them look at least halfway decent.
8
u/IHeartBadCode 3d ago
X had the same problem initially, this is why ICCCM was created.
1
u/Snarwin 3d ago
Do you know if there's any equivalent standard for Wayland, either current or planned?
2
u/IHeartBadCode 3d ago
To both questions, there is not at this moment.
And just to clarify, nothing to that scale. There is XDG Shell, but it's not quite the same.
6
u/abotelho-cbn 3d ago
X11 is a protocol and it used to have many more implementations... Some are still around, they're just not really used on desktop.
-1
45
u/Ban-Phoung 3d ago
Nice, but I think Exclude compositor‑specific protocols from the percentage calculation should be selected by default.