Instead of taking any part in the monthly wayland bashing bullshit, you could just read about how electron, one of the last X11 bastions, has adjusted to wayland. Super important work!

https://www.electronjs.org/blog/tech-talk-wayland

Tech Talk: How Electron went Wayland-native, and what it means for your apps | Electron

Electron recently switched to Wayland by default on Linux, bringing dozens of popular desktop apps along with it. Here's what changed and how it affects developers and users.

@swick The most of the post is about fighting GNOME's absence of server side decorations 😀
@spyke no, they are not fighting it, they are embracing it
@swick Without this "embracing" they could have switched to Wayland several years ago. Not being able to ask the compositor for basic decorations is an unnecessary backward compatibility issue. Podman doesn't look like GNOME and still is on X11. With the same effort it could have been Wayland for at least a year.
@spyke did you read the post?
@swick Of course, fully. That's why I am saying that Wayland already has a lot of breaking changes and not having SSDs only makes migration more difficult. And I am well aware of GNOME's position on that.

@spyke So you read it, and the part where they are now migrating because Chromium, which they depend on, turned on wayland by default. You presumably also used a Chromium based browser in the last few years which is obviously using CSD.

Yet you uttered those absolutely deranged sentences thinking that they might in any way shape or form be true?

@swick Chromium Wayland support appeared not yesterday. And its development has been so slow because it required too much changes at once. Of course, stating that more braking changes means more work is "deranged".