unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "André A. Gomes" <andremegafone@gmail.com>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>, calcium <calcium@disroot.org>
Subject: Re: Planet of Guix-related posts?
Date: Wed, 12 Jan 2022 08:17:41 +0300	[thread overview]
Message-ID: <87h7a95y8a.fsf@gmail.com> (raw)
In-Reply-To: <17e4bf134c1.e66ef4c7366095.6741804581557879420@excalamus.com> (matt@excalamus.com's message of "Tue, 11 Jan 2022 20:40:05 -0500")

Matt <matt@excalamus.com> writes:

>  ---- On Mon, 10 Jan 2022 10:21:51 -0500 zimoun <zimon.toutoune@gmail.com> wrote ----
>
>  > (On a side note between parenthesis, we should avoid to fall into the
>  > "Package Definition" tutorial fallacy; as explained here for monads
>  > https://byorgey.wordpress.com/2009/01/12/abstraction-intuition-and-the-monad-tutorial-fallacy/.
>  > And I wrote one post about monad and another about Packaging. ;-)
>  > However, I think the official documentation has enough materials for
>  > starting to package. End of parenthesis.)
>
> If many people feel inclined to write their own packaging tutorial,
> it's probably an indication that the manual isn't sufficient.  I would
> urge you and others to not fall into the "don't touch it because it's
> good enough for me fallacy".  Others may, and probably do, see things
> differently.

I'd say it indicates that everyone has their own way of assimilating
ideas.  Often times we map things in our minds by means of
simplifications, abuses of languages, imprecisions, etc.


-- 
André A. Gomes
"Free Thought, Free World"


  reply	other threads:[~2022-01-12  5:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.34870.1641617883.18145.guix-devel@gnu.org>
2022-01-08  8:42 ` Guix Documentation Meetup calcium
2022-01-08 11:35   ` Ricardo Wurmus
2022-01-08 11:49     ` calcium
2022-01-08 16:24     ` Matt
2022-01-08 18:58       ` Ricardo Wurmus
2022-01-08 19:06       ` Leo Famulari
2022-01-09 21:12         ` Matt
2022-01-10  9:05           ` André A. Gomes
2022-01-10 13:40             ` Matt
2022-01-10 16:05               ` André A. Gomes
2022-01-11 18:45                 ` Matt
2022-01-12 18:41           ` Leo Famulari
2022-01-13  0:04             ` Matt
2022-01-10 15:21       ` Planet of Guix-related posts? zimoun
2022-01-11 13:38         ` Matt
2022-01-12  1:40         ` Matt
2022-01-12  5:17           ` André A. Gomes [this message]
2022-01-12  8:30           ` Ricardo Wurmus
2022-01-12  9:23             ` Oliver Propst
2022-01-12  8:36           ` Ricardo Wurmus
2022-01-13  0:22       ` Guix Documentation Meetup Leo Famulari
2022-01-13 13:15         ` ilmu
2022-01-08 13:41   ` Matt
2022-01-08 14:09     ` Julien Lepiller
2022-01-08 14:54       ` Matt
2022-01-08 14:39     ` Josselin Poiret

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=87h7a95y8a.fsf@gmail.com \
    --to=andremegafone@gmail.com \
    --cc=calcium@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=matt@excalamus.com \
    /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).