all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Building a software toolchain that works
Date: Thu, 17 Mar 2022 15:04:18 -0500	[thread overview]
Message-ID: <87v8wcs5vh.fsf@gmail.com> (raw)
In-Reply-To: <20220314202659.oftyvymu7tjiycba@thebird.nl> (Pjotr Prins's message of "Mon, 14 Mar 2022 21:26:59 +0100")

I run Guix everywhere I can, and it's now the only way I develop software. Having said that, I have thought about this issue a little bit, and here's my opinion on why this happens.

Pjotr Prins <pjotr.public12@thebird.nl> writes:

>  And they start out as the next new thing to solve all problems! If
> they would only would have used Guix to create a coherent build
> system...

Is Guix not a new thing designed to solve all problems? Why aren't we all just using Nix! Or Make!

The reality is that every new system is created because its creators feel that the available systems are deficient in some way. That opinion may not be shared by everyone.

In addition, because free software is largely developed in people's spare time, they're going to use whatever tools make them most productive or even just happy. They're probably not thinking about their software against the backdrop of the larger software ecosystem.

Finally, build tools which are bespoke to a language or use-case are usually going to be easier to work with because they don't have to consider the general or aggregate cases. So if I only live in 1 ecosystem, I'm going to learn that tool and use it any time I can.

Guix solves a lot of issues, and is wonderful to use, but I don't think it solves the most difficult issues: human issues :)

-- 
Katherine


  parent reply	other threads:[~2022-03-17 20:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 19:05 Building a software toolchain that works Ryan Prior
2022-03-14 20:26 ` Pjotr Prins
2022-03-14 21:40   ` David Arroyo
2022-03-15  8:19     ` Ludovic Courtès
2022-03-17  9:20       ` zimoun
2022-03-16 14:02     ` Josselin Poiret
2022-03-16 15:28       ` Ryan Prior
2022-03-16 20:13         ` Yasuaki Kudo
2022-03-17 15:35     ` Maxime Devos
2022-03-17 16:56       ` David Arroyo
2022-03-14 23:57   ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-15  8:23     ` Ludovic Courtès
2022-03-15  8:42       ` Pjotr Prins
2022-03-15 12:32       ` Yasuaki Kudo
2022-03-17 12:56     ` zimoun
2022-03-18 21:13       ` david larsson
2022-03-18 23:59         ` Yasuaki Kudo
2022-03-19 13:02         ` Windows Subsystem for Linux zimoun
2022-03-24 21:14           ` Ludovic Courtès
2022-03-25  3:43             ` Maxim Cournoyer
2022-03-25  9:04               ` Phil
2022-03-25 10:14                 ` Oliver Propst
2022-03-17 20:04   ` Katherine Cox-Buday [this message]
2022-03-18  6:27     ` Building a software toolchain that works Pjotr Prins
2022-03-18  9:10       ` Oliver Propst
  -- strict thread matches above, loose matches on Subject: below --
2022-03-17 12:06 zimoun

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=87v8wcs5vh.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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.