From: zimoun <zimon.toutoune@gmail.com>
To: "Katherine Cox-Buday" <cox.katherine.e@gmail.com>,
"Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel@gnu.org, guix-science@gnu.org
Subject: Re: “What’s in a package”
Date: Wed, 22 Sep 2021 21:44:02 +0200 [thread overview]
Message-ID: <86h7ec75vh.fsf@gmail.com> (raw)
In-Reply-To: <875yutwuij.fsf@gmail.com>
Hi,
On Tue, 21 Sep 2021 at 15:20, Katherine Cox-Buday <cox.katherine.e@gmail.com> wrote:
> I.e.,
> when trying to achieve a goal, it is a pain to package things that
> aren't yet packaged, but what I get in return are sane environments,
> deployments, and meta-data about all of these.
I concur! :-)
> This is perhaps a rehash of the "worse is better"[2] conversation, but
> I often struggle with deciding whether to do things the "fast" way, or
> the "correct" way. I think when your path is clear, the correct way
> will get you farther, faster. But when you're doing experiments, or
> exploratory programming, being bogged down with the "correct" way of
> doing things (i.e. Guix packages) might take a lot of time for no
> benefit. E.g. maybe you end up packaging a cluster of things that you
> find out don't work out for you. Of course the challenge is: if you
> choose the fast way, and it works out, do you got back to do it the
> correct way so that you're on sound footing?
>
> Bringing this back to Guix, and maybe the GNU philosophy, it has been
> very helpful for me to be able to leverage the flexibility of Guix to
> occasionally do things the "fast" way, perhaps by packaging a
> binary. Paradoxically, it has allowed me to stay within the Guix and
> free software ecosystem. In my opinion, flexibility is key to growing
> the ecosystem and community, and I would encourage Guix as a project
> to take every opportunity to give the user options.
Long time ago, I watched this badly recorded video [1] about “Haskell is
useless”. I reframe for packages the exposed double-axis:
useful | trad-pkg ~~> Nirvana
| ^
| | Guix
useless |
-----------------------
unsafe safe
where ’unsafe’ vs ’safe’ could read ’fast’ vs ’robust’; and trad-pkg
reads apt, conda, spack, yum, etc.
1: <https://youtu.be/iSmkqocn0oQ>
Cheers,
simon
next prev parent reply other threads:[~2021-09-22 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:36 “What’s in a package” Ludovic Courtès
2021-09-21 18:38 ` Arun Isaac
2021-09-22 18:53 ` Pjotr Prins
2021-09-21 20:20 ` Katherine Cox-Buday
2021-09-22 13:32 ` [Spam:]Re: " Konrad Hinsen
2021-09-22 15:02 ` Katherine Cox-Buday
2021-09-22 18:20 ` Konrad Hinsen
2021-09-22 15:44 ` Jonathan McHugh
2021-09-22 19:44 ` zimoun [this message]
2021-09-23 7:36 ` Ludovic Courtès
2021-09-23 15:25 ` Katherine Cox-Buday
2021-09-24 9:04 ` Ludovic Courtès
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=86h7ec75vh.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-science@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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.