So you are volunteering to step up, test and maintain the big endian code? Feel free to grab some PRs and fix them to demonstrate your willingness. This comme

So you are volunteering to step up, test and maintain the big endian code? Feel free to grab some PRs and fix them to demonstrate your willingness. This comment from the article fits: > Having it be an option that's turned off by default just ensures that it will rapidly end up broken because of its "niche"ness, and then removed because it keeps causing breakage. Do it all the way or not at all. The problem is that X11 is actually in a zombie-like state right now. It's not dead because it mostly works, sorta, because people keep stitching extra limbs on when enough people bitch. However, it's not actually alive because nobody really wants to work on it and ... Every single architectural assumption that X11 made is now wrong. CPUs are stupidly powerful. Triangles, not bitmaps, are the fundamental primitive (to be fair, this one may be starting to flip back as GPU computing becomes more ubiquitous). Network is vastly slower than CPU and latency has gotten ferociously worse. Input methods aren't just mouse and cursor. Sharing is a problem and secure should be the default. etc. I have written code for X11. I have written initialization code for graphics cards to deal with X11. X11 coding is hell. Wayland may not be the answer, but X11 needs to die before we will get to that answer.