supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: [Announce] s6.rc: a distribution-friendly init/rc framework
Date: Sun, 25 Mar 2018 06:38:33 +0000	[thread overview]
Message-ID: <em575e093c-7577-4b60-9bc0-d2bb8f658403@elzian> (raw)
In-Reply-To: <20180325045750.GA5868@caspervector>

>On a second thought, what about (at least a attempt at) solving the
>human (political) problems by human means (propaganda, but of the
>factually correct type)?

  It's not a political problem, it's a religious problem. You just cannot
convince people that your UI is better, any more than you can convince
them that your text editor is better. People have tastes, we may find
them bad, but we're not going to change them; trying only paints you
as an annoying zealot, and is counter-productive.

  The factually correct, technically correct solution is already there,
and they accept it, they believe it - we don't need to convince them
of that. It's simply a UI issue. And the right answer to "I like your
engine, but I don't like your UI" isn't "You're wrong, my UI is the
best", it is to put up - and write a UI they like - or shut up.
A major selling point of the s6 and s6-rc formats is that they're easy
to autogenerate, and a frontend would be proof of that. We claim we're
technically better than everyone else, and that our paradigm is more
flexible than others - well there's the opportunity to prove it.

--
  Laurent



  parent reply	other threads:[~2018-03-25  6:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180322132334.GA11596@caspervector>
2018-03-22 17:10 ` Laurent Bercot
2018-03-23  4:00   ` Casper Ti. Vector
2018-03-23 10:09     ` slew: renamed from "s6.rc" Casper Ti. Vector
     [not found]   ` <20180323040022.GA1737@caspervector>
2018-03-23 10:51     ` [Announce] s6.rc: a distribution-friendly init/rc framework Laurent Bercot
2018-03-23 13:05       ` Alex Suykov
2018-03-23 13:31         ` Casper Ti. Vector
2018-03-23 14:19         ` Laurent Bercot
2018-03-23 13:20       ` Casper Ti. Vector
2018-03-25  4:57         ` Casper Ti. Vector
     [not found]       ` <20180323132058.GA21692@caspervector>
     [not found]         ` <20180325045750.GA5868@caspervector>
2018-03-25  6:38           ` Laurent Bercot [this message]
2018-03-25  9:31             ` Casper Ti. Vector
2019-06-03  9:30   ` Casper Ti. Vector
     [not found]   ` <20190603093041.GA10891@caspervector>
2019-06-03 16:06     ` Laurent Bercot
2018-03-22 13:23 Casper Ti. Vector
2018-03-22 15:29 ` Casper Ti. Vector

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=em575e093c-7577-4b60-9bc0-d2bb8f658403@elzian \
    --to=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).