Re: [gentoo-amd64] Boycott Systemd

[Lie Ryan]

On 22 September 2014 10:26, Frank Peters <frank.peters@×××××××.net> wrote:

> I do not use openrc, eudev, or anything similar, and I have no plans
> to ever use systemd.  All of these things are *unnecessary* at present.
> I simply do not need them and do not foresee a time where I will
> ever need them.  In spite of any purported technical superiority they
> still remain *optional*.
>
> My system is booted and configured using my own custom scripts and
> I doubt that anyone would be interested in those.  They work very well
> for me and as a consequence I have no interest in contributing to
> alternatives that I'll never utilize.  (In fact, I would encourage
> everyone to develop his own set of boot/config routines.  It is
> not that difficult.)

Diversity isn't about feeding people who feels everything not-invented
here is godawful. When you have a clearly defined problem and you can
create a solution that satisfies that niche better than any other
solutions, that is diversity. If you just want to keep using your own
stuffs but you don't have a clearly defined niche you want to solve, I
don't have any sympathy for that.

> The concern is that one day this will no longer be possible due to
> the hegemony imposed by players such as those already mentioned.
> I believe that this concern is a valid one.  It will not happen
> overnight but these changes will slowly creep into the Linux
> universe.
>
> My reasons are selfish.  For me (and I'm sure for many, many others
> who just are not aware) implementing these methods are way too much
> work and will bring *no* improvements or benefits whatsoever.
>
> If others need them then others will use them.  But do not destroy
> the ability to forge my own solutions.

If you are not contributing to the solutions I use then don't be
surprised if my software goes to directions that do not accomodate
your own in-house stuffs. There are thousands of people with their own
in-house stuffs that breaks due to the changes, and thousands other
in-house that becomes easier due to the changes, why should I care
about yours in particular. If you want me to care about your stuffs,
then put it in the open, make it useful for more than just you, and
fight it out with other similar solutions.

I never had to deploy a system where the choice of init system makes a
critical difference in the success or failure of the system. I don't
want to spend too much time on configuring init or syslogs or cron
system on every new systems I had to deploy, as long as it does its
job, the rest doesn't really matter. I'll know that I need another
solution when the bog standard doesn't work, but before that happens,
just give me whatever works, and make switching to other systems as
easy as possible.