Blizzard has been looking into Linux, but they aren't making it top priority, same as other game publishers. There is growing interest in Linux and BSD, but nothing concrete due to the chaos going on at the moment with Linux. Right now, BSD is probably going to get more priority thanks to Sony, though I doubt PC versions of games will ever be released.

MS Office will never be ported, period. LibreOffice is already the UNIX-wide standard and the best MS Office could achieve was better compatibility through Wine and CrossOver Office.

In other Pid 1 War news, Debian has decided that...

...

...

... wait for it ...

...

...

... further discussion is needed

A wag on LWN has commented: "This is vastly far from my life right now (in so many ways) but for some reason I can't pull myself away, like the worst, least-gender-balanced soap opera ever. Am I alone?"

The problem is, not all distributions will even benefit from, or can even use systemd to make it usable, feasible, or worthwhile to invest the time and resources to add it in properly. Not all systems use GNOME, X, or even require dbus. Some don't even require udev.

I think Ian at Debian has a good point to ban it's usage. If it's not wanted or needed, don't force the issue.

Without reading anything, the very idea that X (X!) will twist anyone's arm is ludicrous. The sky will fall before X breaks backward compatibility, even for the sake of fixing 20 year old bugs. This is one of the major reasons a new display server had to be developed. And since it has been developed, the chances of X going anywhere are down to zero.

There is nothing at all wrong with having systemd support in Xorg, as long as it is not a hard dependency. Systemd support will help to start X as non-root user on systems that can make use of it.
Seeing that the Xorg developers are in general sane people I really doubt that they will do something like making Xorg dependent on systemd. After all, they didn't do that with Wayland either.

Doesn't X already have non-root start-up support for DRI when you invoke this in xorg.conf?

If that's the case it's nothing but a redundant feature that already is implemented.

KMS/DRI removed the need for being root regarding access to the videocard. Other parts of Xorg still run as root. Also, not all drivers support KMS.

I always run startx as regular user on Slackware. Which help do I need to do that? Do I miss something?

Yes, you miss something. Just try it, after starting X that way:

@TobiSGD: I see, thanks. But then, is that any inconvenience of having root a user of this process, or what would be the advantage of having a regular user instead?

It is a security problem. Running X as unprivileged user is far better from a security point of view.

startx runs /usr/bin/xinit which executes /usr/bin/X which is a link to /usr/bin/Xorg. And /usr/bin/Xorg is suid root.

Nonetheless, I don't see why systemd should need to get involved with how Xorg is run. Wasn't one of the main points of KMS (kernel mode setting) to obviate the need for Xorg to run as root?

It doesn't need to get involved, but it makes it easier.

Yes, it was. The only problem is: Not all drivers (just look at the proprietary Nvidia and AMD drivers) support KMS.

Xorg has a design goal of cross platform support. systemd has a design goal of being of Linux specific enhanced init system.
The premise of this thread is flawed.

systemd allows for multi-seat support under X -that's the connection. Personally, I am happy with my (one) seat...