If Google can add stuff to the protocol that breaks other clients, that sounds like a bug with the protocol more than anything. Why was that even allowed

did Google force them to do that, or did the open source devs just make a mistake?

What’s missing from the article is an actual explanation of how Google “killed” xmpp. Did google force the independent XMPP client developers to not implement cool features or something? Is meta going to buy up and shut down all the independent mastodon instances?

If the problem is that Facebook might develop a superior UX, maybe the fediverse should work on a better UX instead of screaming about some scary boogeyman and how the users are too dumb to know any better?

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.

We get it, you’re straight.

based

People process loss differently.