[Arm-netbook] severe systemd bugs (two of them)

[Bill Kontos]

On Mon, Jul 3, 2017 at 12:06 PM, Luke Kenneth Casson Leighton
<lkcl at lkcl.net> wrote:

>  even with that in mind i see no down-side to the additional workload
> that you refer to when you consider the upside that diversity brings.
> no monoculture, no centralised control, and a need for people managing
> *different* projects - the components that systemd has [irresponsibly]
> made quotes redundant quotes - to communicate, discuss and agree
> interoperable standards.

Because it adds cost technical debt blah blah blah and it is one of
the many reasons as to why applications in gnu/linux systems break all
the time when the maintainer drops them. But I completely disagree
with the idea that adding more people to the mix when they are not
needed is a good thing. It is the fate of everything IT related to
eventually be automated or made redundant and for people to move on to
the next thing. That's just how it is. It used to be office suits
being ported to multiple architectures in the 80s, it's init systems
now. The problem I see with those criticizing systemd is that the vast
majority of them do not even try to make something better that retains
the features that make systemd valuable. Instead they just make a
distro where they purge anything that has systemd in it's name even
when it's a dummy package so packages who expect systemd but can't
find it will work.

Also I don't consider going from a variety of options each with it's
disadvantages to a single option essentially standardizing it a bad
thing. It's just a lost opportunity to make a real standard for sure,
but I don't think that's monoculture.