unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Reorganizing guix package commands
Date: Tue, 19 Apr 2016 08:45:03 -0400	[thread overview]
Message-ID: <8637qhzs1c.fsf@gmail.com> (raw)
In-Reply-To: 878u09j2nk.fsf@gmail.com

Alex Kost <alezost@gmail.com> writes:

> myglc2 (2016-04-19 00:50 +0300) wrote:
>
>> For overall Guix usability, the overloading of a single guix command for
>> everything is not so good. When you eventually create a man page, it
>> will be intimidating for someone just trying to do per-user package
>> management, which the majority of, and least sophisticated users, will
>> be trying to do.
>>
>> On the other hand there are several "classes" of commands as reflected
>> by the guix CLI being described in several logically different parts of
>> the doc. This structure is not so evident in the CLI structure.
>>
>> A possibly better approach would be to explicitly split the guix
>> command-verse into command classes to better match the structure of the
>> doc and/or the class of the user. For example, per-user ('guix ...'),
>> global-system ('guix-sys ...'), and developer ('guix-dev ...'), or
>> something similar.
>
> Sorry, but I can't agree with this.  I don't see a difference between
> "simple users" and developers.  Guix provides many tools indeed, but I
> don't think they should be organized in groups depending on "user
> classes".
>
> I like that all the tools are placed in a single "guix" command, I just
> would like to reorganize it a bit (or a lot :-)).

Yes, of course, you have reacted as I predicted ...

>> While this would be not-so-nice for a power emacs user, ...

But user interface design involves trade-offs. If you design the
interface only for power users that is all you will ever have.

The adjustments I have suggested are easily accommodated by a power user
and meanwhile make Guix much more approachable for a novice.

The problem you face as you set the Guix interface in stone is that you
have inadequate representation of novices in the discussion.

If you are not careful you will harden Guix into a ninja tool and this
will severely limit it's adoption.

You need to remember that, at the end of the day, how important Guix is
will depend on how many users it has.

  parent reply	other threads:[~2016-04-19 12:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  8:57 Reorganizing guix package commands Alex Kost
2016-04-18 16:10 ` John Darrington
2016-04-19  8:01   ` Alex Kost
2016-04-18 17:20 ` Ludovic Courtès
2016-04-18 21:50   ` myglc2
2016-04-19  5:17     ` John Darrington
2016-04-19 12:57       ` myglc2
2016-04-19 13:03         ` Thompson, David
2016-04-19 13:35           ` John Darrington
2016-04-19 13:51           ` myglc2
2016-04-19 15:24       ` Ludovic Courtès
2016-04-19 10:47     ` Alex Kost
2016-04-19 10:58       ` Ricardo Wurmus
2016-04-19 12:45       ` myglc2 [this message]
2016-04-19  7:52   ` Alex Kost
2016-04-19  9:17     ` Taylan Ulrich Bayırlı/Kammer
2016-04-19 10:37       ` Alex Kost
2016-04-19  9:23     ` Hartmut Goebel
2016-04-19 10:16       ` Alex Kost
2016-04-19 14:39       ` John Darrington
2016-04-19 13:00     ` myglc2
2016-04-19 13:43       ` Ricardo Wurmus
2016-04-19 14:29         ` myglc2
2016-04-19 13:55     ` Ricardo Wurmus
2016-04-19 15:52     ` Ludovic Courtès
2016-04-19 19:56       ` Christopher Allan Webber
2016-04-20  3:45       ` myglc2
2016-04-20  5:34         ` John Darrington
2016-04-20  8:52           ` Alex Kost
2016-04-20 17:05             ` myglc2
2016-04-20  8:29       ` Alex Kost
2016-04-20  9:46         ` Taylan Ulrich Bayırlı/Kammer
2016-04-20 21:45           ` Ludovic Courtès
2016-04-21 12:34             ` myglc2
2016-04-21  5:20           ` John Darrington
2016-04-20  9:29       ` Taylan Ulrich Bayırlı/Kammer
2016-04-21  2:49         ` Efraim Flashner
2016-04-21  7:10           ` Taylan Ulrich Bayırlı/Kammer
2016-04-18 21:13 ` Hartmut Goebel

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=8637qhzs1c.fsf@gmail.com \
    --to=myglc2@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).