SystemDicks

It solves a massive nightmare the distros had by getting rid of a lot of 30 year old garbage, works well, and has an active community maintaining it. The trade-off is it's a monolithic blob that is bloated and hard to debug, and the leader of the project is known for attempts to force bad design decisions on everyone. While Debian includes it, they do patch out some of the bigger mistakes. Sadly, they do not disable (un)predictable interface names by default.

Corporate politics. Red Hat wants control. They made systemd and used their influence to promote systemd to the exclusion of all other systems. GNOME jumped on the bandwagon, then everyone who used GNOME had to make a choice and many ended up jumping on the bandwagon too. Then as the bigger distros did that, smaller distros that were more like branches of the big distros followed suit. Systemd has attempted to worm its way into becoming a required dependency of a lot of the linux ecosystem to reduce the degree of freedom people have in avoiding systemd. It's also been applying a lot of bullshit pressure on distros, software packages, etc. (even the kernel, though to no success there) to do things the systemd way. For convenience's sake, a lot of folks have chosen to bend over and get it over with. Nevertheless it is fully possible to run a systemd-free Linux distro, and it will usually run better than the systemd stuff for the precise reason that it doesn't have systemd's extensive bugs, security issues, and instability.

There's a ton that can be said about the dirty ways systemd has been trying to force itself into the linux ecosystem.

It's lovely how you omitted all the dirty stunts systemd has performed to try to force people to adopt systemd. The Embrace, Extend, Extinguish pattern applied to udev as a way of strong-arming Gentoo and the rest of the Linux community into adopting systemd was really quite nasty (and Gentoo forked udev into eudev so they could continue having a systemd-free udev). The way Poettering and pals attempt to submit patches to software packages that would integrate systemd as a necessary dependency for no other reason than to ensure people will have to install systemd to run this software now was also not a subtle attempt to try to force people to install systemd.

The OP's link lists a lot of dirty stuff the systemd project has been up to.

You have to do this to some degree otherwise people who hate change will try to block progress, like how the CAD people killed the proposed modernization of OpenGL and it was something like 10 years before it was attempted again.
The 'hate change' people are lazy, and you'll see that as the distros that refused systemd fail and have to come crawling back because they were dickriding maintenance being done by people now on the systemd project.

I thought Debian and OpenSUSE were NSA, not Arch. Artix is Manjaro-OpenRC merged with another non-systemdicks project IIRC.

nice try lennart, but not all distros are like this.
gentoo maintains(and always has afaik) its own init(OpenRC)

Attached: pottering.jpg (3456x2304, 2.71M)

Yeah, like all the paid shills going

init systems are a social construct

Tell me more about this.

Leave it to systemd fanboys to spout FUD & bullshit about how any non-systemd distro must be a failed distro. Gentoo, Slackware, and Devuan are all still doing great, kid. Try not to be a lying whore; it reflects badly on you.

Yeah, heard that one a bunch too. But honestly if all you want are fast boot times, you really don't need systemd.

How is a small fork of Arch that doesn't even have enough manpower to port/patch all the packages from [extra] and [community] in any way related to the feds?

ayy lmao indeed