From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2 Subject: Re: Reorganizing guix package commands Date: Tue, 19 Apr 2016 08:45:03 -0400 Message-ID: <8637qhzs1c.fsf@gmail.com> References: <874mazi99k.fsf@gmail.com> <877ffual6i.fsf@gnu.org> <86bn56ziw9.fsf@gmail.com> <878u09j2nk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45002) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asV2T-0005oE-LB for guix-devel@gnu.org; Tue, 19 Apr 2016 08:45:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1asV2O-0007vA-Sx for guix-devel@gnu.org; Tue, 19 Apr 2016 08:45:57 -0400 Received: from plane.gmane.org ([80.91.229.3]:58393) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asV2O-0007v6-ME for guix-devel@gnu.org; Tue, 19 Apr 2016 08:45:52 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1asV2N-00013x-C9 for guix-devel@gnu.org; Tue, 19 Apr 2016 14:45:51 +0200 Received: from c-73-167-118-254.hsd1.ma.comcast.net ([73.167.118.254]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 14:45:51 +0200 Received: from myglc2 by c-73-167-118-254.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2016 14:45:51 +0200 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Alex Kost 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.