From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: my latest blog post
Date: Fri, 08 Jun 2018 11:15:16 +0200 [thread overview]
Message-ID: <b0fc40c03daad9e02d8f30353af5a0d0@lepiller.eu> (raw)
In-Reply-To: <CAJ98PDwJOsxVCVGWWZOZsbY=PweLhQvmtFv8BWz4Oo5j+UVzkw@mail.gmail.com>
Le 2018-06-07 17:25, Catonano a écrit :
> I just published my latest blog post
>
> In this post I discuss Guix
>
> And I discuss Guile too
>
> I understand that the language is strong and I expect someone to be
> upset
>
> But I feel this is due
>
> Happy reading
>
> http://catonano.v22018025836661967.nicesrv.de/the-gnu-community.html
Hi,
that was a long but interesting reading :)
I won't be able to address your main points, about the Guile and the
broader GNU
community. That's because even though I'm part of Guix, I haven't really
interacted
with them (yet?). My only interactions were through Guix and a GHM I
attended when
I wasn't a contributor to anything. I remember it as a friendly event
though, so
your post is a bit of a surprise to me. Let me try and address some of
the minor
points instead.
I read you're having trouble to find information from the section
titles. Info manuals
have an index where it's easier to find things. But actually, what helps
me the most
is to ignore the `info` command and open either the full .texi source or
the "html
in one page" version. Then I can do full-text search, which is a lot
quicker. Does
anyone know if there is a similar facility in the info program?
I've also found that GNU documentations were not excessively easy to
navigate.
It's sometimes a bit hard to find information on something fuzzy like
"what's the
function that returns only part of a string again?" or "is there
something that can
grow like a list, but with O(1) access?", but it's a great document to
have when
reading existing code: each procedure is very detailed and in a language
that I find
easy to understand (although it sometimes refers to another part of the
manual).
Ludo proposed to create a separate document for user stories and
tutorials on how
to do specific things, Rekado suggested creating video tutorials
explaining specific
points. I think this is the right direction.
About your concerns on recommending Guix to others, I think you're
mistaken. I actually
discovered Guile through Guix and I haven't have any bad experience. I'm
not on #guile
because people on #guix are generous enough to answer unrelated stupid
questions :)
Guile was even my first functional programming language and I managed to
learn just
enough of it to be able to create packages and system configurations.
All of that
from reading existing code, copying parts that looked related to what I
wanted to do
and not knowing what I was doing at all :). So from experience, you can
use and even
contribute to guix without ever going to #guile. You just need a good
tutorial from the
internet. My point is, if you don't want to recommand the guile
community, you can still
recommand the friendly guix community.
next prev parent reply other threads:[~2018-06-08 9:15 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:25 my latest blog post Catonano
2018-06-07 16:28 ` Joshua Branson
2018-06-08 4:24 ` Christopher Lemmer Webber
2018-06-08 6:18 ` Fis Trivial
2018-06-08 14:02 ` Ricardo Wurmus
2018-06-08 8:25 ` Catonano
2018-06-08 13:51 ` Fis Trivial
2018-06-08 14:25 ` Ricardo Wurmus
2018-06-09 7:47 ` Catonano
2018-06-09 12:24 ` Ricardo Wurmus
2018-06-09 13:07 ` Catonano
2018-06-09 15:29 ` Christopher Lemmer Webber
2018-06-09 13:51 ` Christopher Lemmer Webber
2018-06-07 17:03 ` Mark H Weaver
2018-06-07 19:40 ` Catonano
2018-06-08 9:39 ` Nils Gillmann
2018-06-08 9:45 ` Catonano
2018-06-08 18:05 ` Mark H Weaver
2018-06-09 7:00 ` Catonano
2018-06-09 10:39 ` Ricardo Wurmus
2018-06-09 10:52 ` Catonano
2018-06-09 12:14 ` Ricardo Wurmus
2018-06-09 13:03 ` Catonano
2018-06-10 10:53 ` Mark H Weaver
2018-06-07 18:11 ` Thorsten Wilms
2018-06-07 21:45 ` Alex Vong
2018-06-08 9:15 ` Julien Lepiller [this message]
2018-06-08 9:34 ` Clément Lassieur
2018-06-08 9:45 ` Julien Lepiller
2018-06-08 13:50 ` Widen info Oleg Pykhalov
2018-06-08 13:59 ` Julien Lepiller
2018-06-08 13:49 ` my latest blog post Ludovic Courtès
2018-06-09 5:59 ` Catonano
2018-06-09 22:49 ` myglc2
2018-06-10 0:51 ` Mark H Weaver
2018-06-10 6:55 ` Pjotr Prins
2018-06-10 9:07 ` Catonano
2018-06-10 9:29 ` Ricardo Wurmus
2018-06-10 9:30 ` Catonano
2018-06-10 10:37 ` Ricardo Wurmus
2018-06-10 10:45 ` Mark H Weaver
2018-06-10 12:06 ` Pjotr Prins
2018-06-10 7:58 ` Catonano
2018-06-10 9:26 ` Ricardo Wurmus
2018-06-10 9:27 ` Catonano
2018-06-10 19:13 ` Ludovic Courtès
2018-06-10 8:07 ` Catonano
2018-06-10 19:23 ` Ludovic Courtès
2018-06-10 8:17 ` my latest blog post [everyone, please take a cooldown break] Nils Gillmann
2018-06-10 13:33 ` Christopher Lemmer Webber
2018-06-10 14:18 ` Gábor Boskovits
2018-06-10 14:37 ` Kei Kebreau
2018-06-11 6:01 ` swedebugia
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=b0fc40c03daad9e02d8f30353af5a0d0@lepiller.eu \
--to=julien@lepiller.eu \
--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).