unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: myglc2@gmail.com
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org, Marco van Hulten <marco@hulten.org>
Subject: Re: common software
Date: Mon, 29 Jan 2018 13:40:32 -0500	[thread overview]
Message-ID: <86372o7bkv.fsf@gmail.com> (raw)
In-Reply-To: <87o9lck393.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 29 Jan 2018 18:02:00 +0100")

On 01/29/2018 at 18:02 Ludovic Courtès writes:

> Hi,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>>> Even though there is some subjectivity in what is essential software, a
>>> clean installation of GuixSD is very minimal.  Is there a reason for
>>> this?
>>
>> The reason is primarily that with Guix it is *possible* to do so.  It
>> allows different users on the same system to have different sets of
>> software; as you wrote this is a very subjective decision, so we simply
>> leave it up to the user.
>
> Also, I find it more convenient to have applications I use in
> ~/.guix-profile rather than in the ‘packages’ field of my
> ‘operating-system’: I can install them, upgrade them, etc. whenever I
> want, independently of the system config.

But Ludo’ what is convenient for you is not convenient for the Guix
noob: They are most likely already using a mainstream GNU/Linux distro
on a notebook or desktop. When they try any other distro they expect it
to provide similar stuff to what their distro provided out of the box.
By not doing this we a) fail to meet expectations and b) force them into
the Guix config-o-rama, which, if we are honest, is not friendly: it's
in scheme, far from obvious, and produces errors that helpful only to
someone who already understands Guix.

I remember my own experience 2 years ago: It felt like a religious
purification ritual ;-) What is the benefit of subjecting noobs to this?
Force them onto the Guix path? Send them to Guix boot camp? I don't see
any benefit to the noob of us going this. Do you?

This is why we should change the templates so that GuixSD comes OOTB
with the same stuff as any mainstream distro. IOW, we should quickly get
the noob running GuixSD and only then show them how cool guix-profile
is.

WDYT? - George

  reply	other threads:[~2018-01-29 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 11:22 common software Marco van Hulten
2018-01-28 23:07 ` Ricardo Wurmus
2018-01-29 17:02   ` Ludovic Courtès
2018-01-29 18:40     ` myglc2 [this message]
2018-01-29 19:14       ` zimoun
2018-01-30  0:59         ` Ricardo Wurmus
2018-01-30 10:35           ` zimoun
2018-01-31 19:05             ` pelzflorian (Florian Pelz)
2018-01-29 19:14       ` Ricardo Wurmus
2018-01-30  0:05         ` myglc2

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=86372o7bkv.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=marco@hulten.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).