System D-tritus

For my next certification, I’m getting the Red Hat Certified Engineer.redhat

Since I don’t routinely work in the Red Hat world unlike the other exams I took, it is going to take a lot more studying and time than it did for the others. Don’t get me wrong,  I’ve used Linux and even RHEL, Fedora and other Red Hat-derived Linuxes over the years, but only rarely have I used it at work.

I’ve thus been learning about the latest Linux technologies, and especially systemd.

Jesus Christ, what a fucking mess.

These ignoramuses – typical of modern developers and UX/UI people – have destroyed all usefulness, all sense and just made a worthless system for little gain other than the things they are interested in.

Systemd, in other words, is terrible.

It’s vastly more complicated and fiddly to do everything. It’s a nightmare to configure a runlevel, it’s difficult to add a new service, and in general it’s just insecure. It is awesomely terrible and utterly foul. Only (as I’ve started to call them lately) a typical tech “genius moron” could have come up with something so cretinous.

Typical developer arrogance, in other words.

It kind of reminds me of Microsoft’s PowerShell philosophy, which seems to be, “Why do in 50 characters what you could do in 500 characters?”

The Debian maintainer of systemd recently resigned from the systemd project because he was getting death threats. While I obviously don’t condone death threats, I must admit that learning about systemd sent me into a blind rage of fury at such abysmal technology being grafted into Linux.

While I can learn systemd just like I did PowerShell, it’s an awful trade-off that makes Linux less Linux-like and will end up wasting millions and millions of developer and system admin person-hours on its utter crappiness.