From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: website: say what Guix is at the very top
Date: Wed, 24 Jan 2018 15:19:00 +0100 [thread overview]
Message-ID: <87h8rb1grv.fsf@gnu.org> (raw)
In-Reply-To: <87efmixtl7.fsf@gmail.com> (Chris Marusich's message of "Sun, 21 Jan 2018 23:04:20 -0800")
Hello,
Chris Marusich <cmmarusich@gmail.com> skribis:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Hi Guix,
>>
>> on the website it starts right away with a list of features:
>> “Liberating”, “Dependable”, and “Hackable”. But what is this thing
>> called Guix?
>>
>> We should add a very short paragraph above that list to say what Guix
>> and GuixSD are.
>>
>> What do you think?
>
> How is Guix different from other package managers? Why is it better?
That’s what Liberating (free software), Dependable (transactional,
etc.), Hackable (it’s a Scheme API) tries to convey.
The hope was that by reading these 3 items people could tell how it
differs from APT/dpkg, Conda, or Nix.
> Perhaps the best way to do that would be to write a problem statement.
> Instead of explaining what Guix is, explain what problems Guix solves.
> The first chapter of Eelco Dolstra's Ph. D. thesis [1] did a fantastic
> job of explaining what problems Nix solves, and by the end of that
> chapter, I was really excited to learn more about Nix (and Guix) and try
> it out. In particular, the list of problems with the state of the art
> in section 1.3 "Motivation" and the list of solutions that Nix offers in
> section 1.5 "Contributions" were particularly concise and convincing.
> Maybe we can aim for something similar on our Guix website?
The “Introduction” and “Features” sections of the manual aim to achieve
that goal, but in a “constructive” way (stating what properties it has,
rather than what properties other solutions lack.) However, I think
it’s not that concise and it’s quite technical, so I’d keep that in the
manual rather than on the front page.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2018-01-24 14:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:30 website: say what Guix is at the very top Ricardo Wurmus
2018-01-17 18:08 ` Tobias Geerinckx-Rice
2018-01-19 8:04 ` Ricardo Wurmus
2018-01-21 17:11 ` Tobias Geerinckx-Rice
2018-01-19 6:09 ` George myglc2 Clemmer
2018-01-19 7:42 ` Ricardo Wurmus
2018-01-19 13:32 ` Ludovic Courtès
2018-01-19 20:35 ` myglc2
2018-01-21 14:47 ` Ricardo Wurmus
2018-01-24 5:54 ` myglc2
2018-01-24 14:24 ` Oleg Pykhalov
2018-01-24 14:22 ` Ludovic Courtès
2018-01-26 23:03 ` myglc2
2018-01-27 16:14 ` Ludovic Courtès
2018-01-27 18:20 ` myglc2
2018-01-27 21:59 ` Pjotr Prins
2018-01-28 16:24 ` Ricardo Wurmus
2018-01-29 4:14 ` myglc2
2018-01-29 7:37 ` Pjotr Prins
2018-01-29 21:31 ` Cook, Malcolm
2018-01-29 22:20 ` Ricardo Wurmus
2018-01-29 22:24 ` Cook, Malcolm
2018-01-30 1:03 ` Ricardo Wurmus
2018-01-30 22:17 ` myglc2
2018-01-30 1:43 ` George myglc2 Clemmer
2018-01-30 2:56 ` Ricardo Wurmus
2018-01-30 7:31 ` Pjotr Prins
2018-01-30 7:46 ` Pjotr Prins
2018-01-31 16:58 ` myglc2
2018-01-31 17:27 ` Pjotr Prins
2018-01-31 18:11 ` myglc2
2018-01-31 18:13 ` Pjotr Prins
2018-01-28 0:35 ` Chris Marusich
2018-01-22 7:04 ` Chris Marusich
2018-01-22 16:43 ` myglc2
2018-03-16 7:14 ` Pjotr Prins
2018-01-24 14:19 ` Ludovic Courtès [this message]
2018-01-28 0:33 ` Chris Marusich
2018-01-28 21:58 ` Ludovic Courtès
2018-01-29 2:08 ` Chris Marusich
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=87h8rb1grv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@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 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.