I think KDE devs are of the same opinions about layer-shell. There was also talk about restricting what kind of windows can be created with this protocol so that fullscreen overlays are not possible (because they can be abused for nefarious purposes). Not sure if it was implemented.
There was also talk about restricting what kind of windows can be created with this protocol so that fullscreen overlays are not possible (because they can be abused for nefarious purposes). Not sure if it was implemented.
A permission system, similar do Android’s “Allow to appear on top?” is the actual solution to that problem. Disclaimer: No idea if anybody (KDE or otherwise) implemented it.
I’ve seen some statements with absolutely zero self-awareness, but this is taking the fucking piss. Factorio had to add an additional dependency to get the game to work on GNOME because GNOME refused to implement server-side decorations.
The GNOME dev could have been more congenial but their point is a fair one. Having a major app developer using a private API would mean that any time that private API is changed or removed, the app gets broken and everyone thinks it’s GNOME’s fault. This is the whole reason there is a public/private distinction in APIs.
Discord isn’t exactly a small app developer. They don’t have an excuse not to do things properly.
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.
the GNOME maintainers would’ve ripped a huge fart, sniffed it and said “usecase??” while closing the issue, as they’ve done for years.