From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Elisp addiction not as bad in light of Linux forkoholism
Date: Mon, 01 Dec 2014 12:56:24 -0500 [thread overview]
Message-ID: <m5ia3n$4ar$2@dont-email.me> (raw)
In-Reply-To: 87k32caad9.fsf@kuiper.lan.informatimago.com
"Pascal J. Bourguignon" <pjb@informatimago.com> writes:
> Dan Espen <despen@verizon.net> writes:
>
>> "Pascal J. Bourguignon" <pjb@informatimago.com> writes:
>>
>>> I've not looked at systemd too closely, but AFAICS, the problem is not
>>> child-diseases, but more that it's not enough unixy.
>>
>> It's like an echo. I keep reading this same opinion.
>>
>> 1. I don't know much about it
>> 2. It's bad.
>>
>> Spend a little time appreciating the simplicity of systemd
>> and then reach your conclusion. In my opinion, the design is
>> good and it takes a whole bunch of disorganized shell scripts
>> and turns them into data. I nice simple, readable data structure.
>
> Notice that you're the first one I read expressing this judgement about
> systemd. It's certainly encouraging to have a closer look at it.
Seems to me we have a culture that encourages disparaging everything.
I do notice that common pattern of the people bad-talking systemd
all starting out with "I don't know much about it".
That encouraged me to take a look.
I had no reason to look before then because I had no problems working
with it. I noticed some commands changed, but they worked perfectly.
One of the primary attributes of systemd is that it took a whole bunch
of daemon admin scripts, found the commonalities, then replaced
them with data files.
This attitude that I know better than the experts is dumb.
At least learn something before you open your mouth.
(Not you, the generic you.)
--
Dan Espen
next prev parent reply other threads:[~2014-12-01 17:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 0:06 Elisp addiction not as bad in light of Linux forkoholism Emanuel Berg
2014-11-30 1:22 ` Filipp Gunbin
[not found] ` <mailman.14979.1417310548.1147.help-gnu-emacs@gnu.org>
2014-11-30 1:49 ` Emanuel Berg
2014-12-01 12:17 ` Filipp Gunbin
[not found] ` <mailman.15048.1417436297.1147.help-gnu-emacs@gnu.org>
2014-12-12 2:07 ` Emanuel Berg
2014-11-30 5:16 ` Pascal J. Bourguignon
2014-11-30 6:05 ` Dan Espen
2014-11-30 14:56 ` Emanuel Berg
2014-11-30 17:04 ` Pascal J. Bourguignon
2014-12-01 17:56 ` Dan Espen [this message]
2014-12-01 18:41 ` Rostislav Svoboda
[not found] ` <mailman.15078.1417459356.1147.help-gnu-emacs@gnu.org>
2014-12-01 20:13 ` Dan Espen
2014-12-12 2:09 ` Emanuel Berg
2014-11-30 14:51 ` Emanuel Berg
2014-12-12 3:42 ` Emacs and Unix (was: Re: Elisp addiction not as bad in light of Linux forkoholism) Emanuel Berg
2014-11-30 16:14 ` Elisp addiction not as bad in light of Linux forkoholism Marcin Borkowski
[not found] ` <mailman.15000.1417364114.1147.help-gnu-emacs@gnu.org>
2014-11-30 17:35 ` Emanuel Berg
2014-11-30 18:36 ` Marcin Borkowski
2014-11-30 19:27 ` H. Dieter Wilhelm
[not found] ` <mailman.15012.1417375681.1147.help-gnu-emacs@gnu.org>
2014-11-30 19:43 ` Emanuel Berg
2014-11-30 20:18 ` Marcin Borkowski
[not found] ` <mailman.15021.1417378703.1147.help-gnu-emacs@gnu.org>
2014-11-30 22:21 ` Emanuel Berg
2014-11-30 22:30 ` H. Dieter Wilhelm
[not found] ` <mailman.15028.1417386648.1147.help-gnu-emacs@gnu.org>
2014-12-12 1:55 ` Emanuel Berg
[not found] ` <mailman.15006.1417372637.1147.help-gnu-emacs@gnu.org>
2014-11-30 19:41 ` Emanuel Berg
2014-11-30 18:16 ` Nikolay Kudryavtsev
[not found] ` <mailman.15002.1417371387.1147.help-gnu-emacs@gnu.org>
2014-11-30 18:32 ` Emanuel Berg
2014-12-02 14:50 ` Raffaele Ricciardi
2014-12-02 15:07 ` Eli Zaretskii
[not found] ` <mailman.15150.1417532856.1147.help-gnu-emacs@gnu.org>
2014-12-02 16:01 ` Loris Bennett
2014-12-02 17:00 ` Eli Zaretskii
2014-12-03 1:44 ` Stefan Monnier
[not found] ` <mailman.15187.1417571105.1147.help-gnu-emacs@gnu.org>
2014-12-12 2:38 ` Emanuel Berg
2014-12-12 2:17 ` Emanuel Berg
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='m5ia3n$4ar$2@dont-email.me' \
--to=despen@verizon.net \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).