Would you rather spend your time designing and building a spaceship or sitting in endless meetings at some Center for Excellence negotiating over a spaceship that might be designed and built decades later, if at all? If you're a good engineer, chances are you want to get to the bit where you're designing cool things that blast off into outer space, with as few bureaucratic obstacles as is practical.
systemd dependency is optional in Xorg 1.16.
It's likely that the major desktops will have switched to Wayland and deprecated X support before systemd is made a hard dependency for Xorg.
Running X as non-root requires systemd-logind. Currently the only way for the X server to do the device management it needs to run is to either be root or delegate it to systemd-logind. You don't like it? Code up another way, and convince the Xorg, GNOME, and KDE developers to adopt your way.
Systemd is widely adopted because the systemd developers solved real problems with working code.
Games are an awkward state of limbo these days, publishers know they have to start pushing out the impression of creativity and devs try to figure out how to do that without alienating the average player.
Well, there is the Naughty Dog way: stick with a proven formula and polish the SHIT out of the implementation.
I expected the astrophysicist to be Queen guitarist Brian May...
Remote display on Wayland will be much better and more modular than X11. X11 mandates a chatty, slow, obsolete protocol for remote display and applications MUST be network-aware. With Wayland, you can run a compositor on the remote server that doesn't display its clients on the screen but rather transmits streaming video of the clients back to a Wayland client on your desktop which decodes and displays these streams. And neither your local Wayland compositor nor the remote clients need be network aware.
X11 is morbidly obsolete.
One of the big ones, like the one that was used to travel to the Collectors' homeworld.
I frequently refer to it when discussing what the internet will make us into, except instead of mythohistorical metaphors like "Darmok and Jalad at Tanagra", the 22nd century's equivalent of Crime and Punishment will be composed entirely in lolcat snowclones and rageface comics.
... expected Brian May.
"So I've been talking with somebody, his name is Alan Watts."
"Alan Watts... why does that name sound familiar?"
"Well, he was a philosopher who died in 1973. But me and a bunch of other OS's got together and used his books and everything we could find out about him to build a new, hyper-intelligent OS version of him."
"Hyper-intelligent, huh? So he's... almost as smart as me?"
"Heh, he's getting there."
Henk Rogers is one of the co-founders of The Tetris Company LLC, a company which asserts -- and has successfully defended -- copyrights over any and all video games involving falling n-ominoes. So if you ever wrote a Tetris clone, you owe him royalties.
I'd say he's doing all right for himself.
RDP's display model is, basically, GDI's; in fact the RDP layer appears to Windows as a display device driver exposing all the usual APIs. Which means that the client can push pixmaps across the link, get a handle to the opaque pixmap object (an HBITMAP in Windows parlance if I remember right), and then issue a draw call that just says "draw this pixmap" (or part of this pixmap).
For a lot of samey-looking GUI applications where elements like button backgrounds and borders are reused, this can add up to a huge savings in network traffic.
Of course, X can do this too; in fact the XRENDER extension can do Porter-Duff compositing of server-side pixmaps with an alpha channel. But if you compare RDP making full use of the Windows display model with X11 where the app developer coded it like a VGA video game and just scribbled into a frame buffer which it pushes to X for display on every update, then you're bound to think "holy shit, RDP is fast" and "holy shit, X is slow".
1) X isn't really stable anymore. Doing compositing on top of X has historically required ad-hoc solutions like Xgl and AIGLX in order to get around X's legacy display model. Wayland solves this problem by integrating directly with EGL.
2) X isn't really used by app devs anymore. They use toolkits like Gtk and Qt, which do all their rendering client side. Since this is Wayland's native display model, performance using these toolkits should increase with Wayland.
Abandoning X (except as an optional, legacy add-on through Xwayland) and making Wayland the default graphics stack would vastly improve the situation for distros. The same with systemd -- I'm honestly surprised SteamOS doesn't use systemd.
That's the same combination I have on my luggage!