From: ng0 <contact.ng0@cryptolab.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Services: gnunet. (require help)
Date: Mon, 23 Jan 2017 11:53:56 +0000 [thread overview]
Message-ID: <874m0qvvor.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87efzwowng.fsf@gmail.com>
Chris Marusich <cmmarusich@gmail.com> writes:
> ng0 <contact.ng0@cryptolab.net> writes:
>
>> Compared to OpenRC and systemd, shepherd guixsd-specific services
>> sometimes have an high learning curve.
>
> Honest question: why do you think that? With feedback from a fresh
> perspective like yours, maybe we could think of ways to lower the
> learning curve.
>
> --
> Chris
I will try and reflect on OpenRC in a while and compare it to
Guix-specific Shepherd (I don't know generic shepherd yet).
For now all I can say is that it's exciting and motivating to
learn a language and grammar which is usable outside of package
definitions or service definitions.
Guile's way to print errors makes it hard, that's one thing.
Another thing is, strange enough, the freedom. You have some
rules you have to obey, but beyond that you can express what you
want. OpenRC, if I remember correctly, was more strict about how
you compose things (but then again last time I wrote something
for Gentoo OpenRC (not even downstream OpenRCs) was the guix
daemon service and that was awful enough to promote it as
fundamentally broken (openrc gnunet service was easier and
worked).
Comparing side by side or in reflection will be easier.
--
♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-23 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:50 Services: gnunet. (require help) contact.ng0
2017-01-18 16:50 ` [PATCH] gnu: services: Add gnunet-service contact.ng0
2017-01-20 13:26 ` Services: gnunet. (require help) Ludovic Courtès
2017-01-21 12:04 ` ng0
2017-01-21 22:50 ` Chris Marusich
2017-01-23 11:53 ` ng0 [this message]
2017-01-23 12:08 ` Ricardo Wurmus
2017-02-24 21:48 ` ng0
2017-02-24 21:53 ` ng0
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m0qvvor.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).