

Interesting implication, but you’ll note that I’m not one of the posters to this particular issue.
And since when is “this is a feature GNOME is lacking” a pissing contest? I’ve seen real spam in a bug tracker. This isn’t it.


Interesting implication, but you’ll note that I’m not one of the posters to this particular issue.
And since when is “this is a feature GNOME is lacking” a pissing contest? I’ve seen real spam in a bug tracker. This isn’t it.


Exactly this. When I was writing up discover overlay i saw their stance “make it an extension” and decided I didn’t have time to rewrite from scratch to appease Gnome. There’s a workaround or nothing.


https://wayland.app/protocols/wlr-layer-shell-unstable-v1
This interface should be suitable for the implementation of many desktop shell components, and a broad number of other applications that interact with the desktop
Suitable. Not strictly, and certainly not private. Everyone else, KDE included, have managed to make this work fine.
I might add that I’m quite well aquianted with this protocol as it comes up in a lot of projects I’m involved with.


What private API? Layer shell is a defined spec they just need to pull their fingers out and let the user opt in to it.


Ah yes, API abuse. Which is when you use the API as intended and written.
Gnome devs are completely out of touch.
As a dev who regularly relies on GTK… I jumped to the correct conclusion