Good thing you grew out of being a toxic self-aggrandizing egoist! This blog post wasn't about you; it's about Wayland community memes. But sure, let's make it about you. Let's go point by point; it's your favorite hobby, after all.

Point 1: “Wayland can’t be keylogged, unlike X11.” False. The meme doesn't present much context; it presumes that keylogging only proceeds through the client APIs of Wayland and X11. The implication is that X11 is horribly insecure and allows arbitrary keylogging, or something along those lines. But of course keylogging can happen at many levels, and as you yourself point out, those levels are largely independent of the compositor. As a result, Wayland can be keylogged exactly like X11.

It's not even fair to try to make this comparison apples-to-apples, since X11 and Wayland have different network-transparency properties, which inherently means that their protocol weaknesses entail different bug classes. This point seems to be ignored by everybody, though, so perhaps it's worth ignoring here too.

Point 2: “Wayland is highly compatible with any hardware, including mobile.” False. Simply false. Your defense is a hedge maze and I won't put up with that bullshit from you today. nVidia cards are a non-trivial percentage of the PC market and nVidia as a vendor is extremely hostile towards people using their cards with FLOSS. (You yourself whine about this elsewhere in-thread.) In addition, most ARM vendors are unwilling to cough up datasheets and few of them are providing good-enough FLOSS drivers. (nVidia doing better on the Tegra front than their consumer GPU front here is pretty funny.)

Psychology alert! The use of universal language combined with hedges and dodges is indicative of a narcissistic perspective. The speaker is more interested in being correct than in learning about nuances. This meme's a good example of this sort of thinking; whoever said this is more interested in proving that wlroots is always the right answer than in actually doing the research and building up a compatibility table and detailing the nuanced differences between hardware. Hmm, I wonder if anybody actually does that for GPUs? [0][1][2][3] The sad truth is that you've been kicking the biggest and worst parts of hardware compatibility to the driver authors for a long time and then crowing and then awarding yourself medals for writing a DRM interface as if it's not a 200-lines-of-Python task.

You could improve this situation. Start by actually measuring compatibility with different hardware. Collect user reports. Build a table.

Point 3: “Wayland removes legacy cruft which makes it easier to maintain.” False. Wayland is explicitly not a modernization of X11. The actual upstream page for work on replacing X11 with a theoretical X12 protocol is at [4]. Wayland is simpler than X11 because it fundamentally only covers a small slice of X11's API, and at that, mostly only specific graphical extensions like XRender and GLX, with nearly all of the core X11 APIs having no analogue in Wayland. I recognize that you may not find the X11 core API valuable, but you did not replace it with anything!

Point 4: “Wayland has fewer bugs than X11.” Not even false. Seriously, you wanna defend this stupid utterance? It's pretty obvious flamebait used by Wayland fans to attack people who haven't converted over to the new religion.

In summary, check your ego already. You'll never be krh.

[0] https://www.x.org/wiki/RadeonFeature/

[1] https://nouveau.freedesktop.org/wiki/FeatureMatrix/

[2] https://www.x.org/wiki/GalliumStatus/

[3] https://www.x.org/wiki/IntelGraphicsDriver/

[4] https://www.x.org/wiki/Development/X12/