all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Simon Josefsson <simon@josefsson.org>, guix-devel@gnu.org
Subject: Re: advanced?
Date: Sun, 27 Nov 2022 10:35:13 -0800	[thread overview]
Message-ID: <878rjw5jq6.fsf@contorta> (raw)
In-Reply-To: <875yf1qtfq.fsf@latte>

[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]

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

  Please avoid marketing phrases such as “world-leading”,
  “industrial-strength”, and “next-generation”, and avoid superlatives
  like “the most advanced”—they are not helpful to users looking for a
  package and may even sound suspicious. Instead, try to be factual,
  mentioning use cases and features.

I'm just not sure what stating "advanced" up-front really adds or
improves a brief statement about what guix is...

Reading through your patch, it just seems like an extra word thrown in
hoping for the positive connotations and possibly dragging in some
negative ones (e.g. elitist, not for everybody).

It also makes me wonder if "advanced" will stand the test of
time. Someday Guix-style systems might just be status quo, and thus no
longer advanced. Guix of course will likely evolve over time... maybe it
will still hold qualities worthy of being called "advanced", maybe not.

Reminds me of when I used to work at a computer re-use and recycling
organization, and we would routingly get computers with stickers on them
proclaiming "Blazing fast 400MHz processor" and the likes. Marketing
phrases quickly loose context.


> 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.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2022-11-27 18:36 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 ` Vagrant Cascadian [this message]
2022-11-28 11:18   ` advanced? Ludovic Courtès
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

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

  git send-email \
    --in-reply-to=878rjw5jq6.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=simon@josefsson.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.