From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Simon Josefsson <simon@josefsson.org>, guix-devel@gnu.org
Subject: Re: advanced?
Date: Mon, 28 Nov 2022 12:18:48 +0100 [thread overview]
Message-ID: <874juje38n.fsf@gnu.org> (raw)
In-Reply-To: <878rjw5jq6.fsf@contorta> (Vagrant Cascadian's message of "Sun, 27 Nov 2022 10:35:13 -0800")
Hello!
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2022-11-26, Simon Josefsson via "Development of GNU Guix and the GNU System distribution." wrote:
>> I find use of the term 'advanced' wrt Guix confusing and even mildly
>> excluding, even though it is wide-spread. What is advanced about Guix?
>> Can I use it even if I'm not an advanced user? What do others think?
>> Is there some historical background for this description of Guix?
>
> Thanks for bringing this up!
>
> It does seem consistent with the guix manual section on package synopsis
> and descriptions:
>
> https://guix.gnu.org/en/manual/devel/en/guix.html#Synopses-and-Descriptions
Indeed. :-) I’m fine with the patch Simon submitted and agree with the
rationale.
[...]
>> If we want to use the term, I think it would be better to rephrase
>> things as 'Guix supports advanced features such as X, Y and Z' if we
>> really want to drive home that we are advanced.
>
> This works for me... describe *why* it is advanced rather than just
> proclaiming it.
The second and third points (dependable and hackable) give an idea of
what makes it advanced, so maybe we don’t need to add much?
Or if we do want to explain more, then perhaps we need a list of
features that would also include things like Docker/VM image generation,
declarative home environments, etc. But that’s broader topic.
Thanks,
Ludo’.
PS: For the record, the phrase “advanced distribution of the GNU system”
was coined by RMS at a time where he insisted that this thing cannot
be called “the GNU system”. All this makes little sense, even less
so today, but if you’re curious you may enjoy Andreas’ entertaining
talk: https://10years.guix.gnu.org/video/ten-years-of-failures/
next prev parent reply other threads:[~2022-11-28 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 21:47 advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-27 8:51 ` advanced? Liliana Marie Prikler
2022-11-27 12:39 ` advanced? zimoun
2022-11-27 17:22 ` advanced? Ryan Prior
2022-11-27 18:35 ` advanced? Vagrant Cascadian
2022-11-28 11:18 ` Ludovic Courtès [this message]
2022-11-28 14:44 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 18:36 ` advanced? zimoun
2023-01-04 11:00 ` advanced? Ludovic Courtès
2023-01-09 12:02 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 15:35 ` advanced? Denis 'GNUtoo' Carikli
2023-01-04 10:54 ` advanced? Ludovic Courtès
2023-01-09 11:12 ` advanced? Ludovic Courtès
2023-01-09 11:37 ` advanced? Julien Lepiller
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=874juje38n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=simon@josefsson.org \
--cc=vagrant@debian.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).