https://news.itsfoss.com/wayland-core-protocol-issue/
Wayland is a display server system based on the idea of protocols. That means there is no Wayland display server that clients need to talk to. Instead, Wayland defines a protocol for creating display servers. Any client application programmed to use this protocol can work on any display server(or
![Wayland Core Protocol is Tailored Only for GNOME and That's Not a Good Thing [Opinion]](https://discuss.tchncs.de/pictrs/image/e83d644c-176d-49a2-97a5-7b0e2be8c0ac.png)
It’s impossible to create cross-desktop desktop components like plank and latte dock.
What nonsense. This is why layershell exists. If there's a problem, its that GNOME's architecture doesn't decompose the compositor and desktop apart. That's not a wayland issue, that's just GNOME's design. There's also nothing in this writeup that really explains why it is "impossible" to do what is clearly already done.
So instead of having a function for moving the window, which would had been useful in many cases, they resorted to having a function only useful for implementing CSD.
Actually, having other rogue wayland clients randomly decide to move your windows around is a really bad idea. Author fails to name any one such useful case.
It turns out that GNOME’s influnece on uptsream Wayland has not brought any benefits to the platform, they just stand as a gate keeper prveneting the addition of other opionions and ideas.
Garbage take. GNOME doesn't get to decide what extensions KWin supports, just as KWin doesn't dictate GNOME's support.
A whole laundry list of complaints that aren't based in reality.