killing X11

Killing X11 by Ted Unangst
==========================

X11 is supposed to be dead, but people keep using it because
apparently it still works. I have a plan to fix this so everyone does
what I want.

It all starts with a popular toolkit library like QTK. Even if people
don't upgrade X11, if they run a browser, they're on the upgrade
treadmill.

I change the internal pixel representation from RGB to BGR and adjust
the Wayland backend, but not the X11 backend because that's community
supported.

I am confused when bug reports start coming in. Weird colors on X11?
Doesn't surprise me, there's tons of weirdness in that pile of jank.
Works for me in Wayland, you should try it.

Somebody will figure it out and submit a patch. I'm sorry, but we
have a release scheduled and we can't merge anything that may cause
further regressions, even though it only changes x11.c. Are we sure
this is even the correct fix? Have you tested with a Voodoo2 card?

This is the internet, so after sufficient slow walking, someone is
bound to say something unpleasant on the tracker. I write a blog post
outlining how not only is X11 support a burden on developers, it's
literally unsafe. Just look at these death threats.

I commit the fix with a lengthy commit message fanfic story about
frogs and scorpions and the Jem'Hadar.

I revert the BGR change back to RGB pixels. I write another blog post
expressing regret about the lack of progress and alluding to all the
cool things that would have been possible, if only we weren't held
back by legacy platform support. No need for details, people will get
the message.

Users start reporting bugs on X11. Weird colors on X11? Again? How
many times do we need to fix this crap? We need to get people off of
X11, whatever it takes.

I devise a plan to kill X11.

From: <https://flak.tedunangst.com/post/killing-X11>