zapper wrote:

Btw, if systemd theoretically was the lesser of two evils, what the hell has this world become!

Presumably the only other choice would be Windows.

That both makes sense and sounds awful.

zapper wrote:

Btw, if systemd theoretically was the lesser of two evils, what the hell has this world become!

Presumably the only other choice would be Windows.

That both makes sense and is a pathetic situation.

>.>
<.<

Btw, if systemd theoretically was the lesser of two evils, what the hell has this world become!

Presumably the only other choice would be Windows.

O.o

That sounds like a nightmare.

Imagine how much more bloated the other alternative would be.

xD

My turning point with Systemd was when it slowed down my surfing by taking over the resolver. Systemd created a lag and it was unacceptable to me. I already knew about its history and Poettering, so since then I've been waiting to transition completely to Devuan.

For me, it was more of a suspicion coupled with reasoning.

I heard about the debian/devuan situation announcement early in its fork around the time I was using trisquel gnu/linux.

I heard that archlinux around that time and fedora previously had tried and failed in this endeavor. Although I know now that archlinux, has a variant known as obarun so... not so much like I thought.

But I looked into arguments on the against systemd side because I wondered what reasoning they had.

Half a year or so passed and I decided to check into a few things. Sure enough, systemd was a huge package.

Around that time I thought to myself, the more amount of code, the more complex it is, it must also be harder to find the bugs.

Even if you have a million people working at it, 1 million lines of code, must be a mess to debug.

Having  four to eight thousand lines of code however, or similar like openrc, or others which have less, probably takes less people to find those problems.

If this is the case, why bother with an over-engineered concept when a simpler concept would take way less debugging and have a lot less problems?

Also, I scoured a bunch of the systemd bugs from certain websites like nosystemd and without-systemd, etc...

when it boiled down to it, I realized the unix philosophy was by far superior.

And the question became, what drugs made people think it was a good idea to bloat an otherwise good idea?

Then it came to me as time passed:

Greed and power

Both of which are completely unreasonable reasons to do this.

Besides, its only short term profit that will later come back to bite everyone and arguably as I said elsewhere, the planet itself.

PS, for those who don't believe in climate change, you don't have to believe it. It can still do damage whether you know it is happening or not.

Feelings do not equal facts.

How low have we fallen to be discussing a reddit thread here . . . seriously . . . worst place ever for accurate information . . .

Nah, we could still fall lower, we could be discussing, tik tok videos, or stuff from discord.

OT: Open letter to the Linux World
Date: Tue Aug 12 2014 - 15:35:49 EST
https://lkml.iu.edu/hypermail/linux/ker … 02496.html

Systemd: The Biggest Fallacies by Jude C. Nelson
https://sysdfree.wordpress.com/2018/03/26/186/

General Resolution: init system coupling
https://www.debian.org/vote/2014/vote_003

Combatting revisionist history
2015-02-25 20:23
https://forums.debian.net/viewtopic.php?t=120652

So is it like better of the two devils situation here? I actually like sysvinit better, but let's not call a spade a spade, is systemd that bad?