It's truly fascinating and interesting to read peoples thoughts on Slackware and systemd. And I appreciate that it's so civilized, philosophical and technical. Although there are some skirmishes here and there, which is fine for me since it gives me a laughter or two.

It would be even more interesting if there was some sort of study to read on the philosophical and technical aspects of SysVinit and Systemd, and a detailed comparison of the two systems.

I use Slackware on my Asus laptop, with broken hinges but thank G-d the lid is aluminum so you can put screws through it, and on my AMD server with lowest specs available. I like SysVinit because it's so simple, at least for my uses, as well as Slackware. But I guess there must be some use cases on corporate level since Systemd has been developed.

When it comes to choice I think it's good that there are several init systems out there. Sadly we only have one kernel to chose from, which is strange, I guess, since there are so many distros and other software out there.

Also, I read that a group of people has gotten together to keep eudev alive. That's fantastic. I wonder how these people meet. I would like to help out with my extremly limited knowledge but I don't know who to contact.

2 members found this post helpful.

Regarding simplicity: we don't expect this in a user application like firefox or write. These programs are genuine Swiss army knives, and need to be so for user convenience.

It's a different matter for basal software, the guts of your OS. UNIX was designed at a time when you got your OS with the machine and then had custom applications written for you by a software company. The simpler the OS was internally, the less chance there was of the machine going belly-up during use. Unixen are made of a few simple bits that coordinate to give you your user experience: kernel, C library, other basic libraries, init, shell, utilities (and optionally the X-server and a window manager). Keeping these as simple as possible, with each bit doing one job, makes your system robust and easy to understand. Having a very complex collection of programs as your init doesn't really make sense.

7 members found this post helpful.

User space is a free for all. Users can, (and should), be able to do whatever they want. User-land programs might integrate well together, or they might not. Either way, they should never integrate with the system. (I'm looking at you Edge).

System space is sacrosanct. The fact that Slackware respects this is the reason that it has rock solid stability and bulletproof reliability.

3 members found this post helpful.

Actually, I was mimicing you and fully aware of what I was doing. You're getting real boring and somewhat of a nuisance, so I'm going to put you on ignore like I did your "friend".

Just friendly advice, you could try a less hostile and more friendly approach in general in the future.

5 members found this post helpful.