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: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Opining on "modern" development practices (was Re: Merging the “binary” NPM importer?)
Date: Thu, 28 Oct 2021 10:01:39 -0500	[thread overview]
Message-ID: <87lf2d9orw.fsf@gmail.com> (raw)
In-Reply-To: <87lf2mxj4a.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 21 Oct 2021 21:39:33 +0200")

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Katherine,
>
> Katherine Cox-Buday <cox.katherine.e@gmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> It’s an unusual situation, but it seems that “modern” development
>>> practices make it hard or impossible to meet our standards in the first
>>> place; yet, we’re missing out on a whole range of free software packages
>>> by not doing anything.  Offering the tool while not compromising on our
>>> standards seems like a reasonable middle ground.
>>
>> I think this is yet another example of the "worse is better"[1] debate,
>> seemingly still ongoing in the world, thirty years later.
>>
>> I don't have much practical to say on the subject, but a few things have often
>> occurred to me which someone may find useful or interesting to ruminate on:
>>
>> 1. The premise of the "worse is better" philosophy seems to me to have been
>>    proven true. Development tools and environments which are easier to get,
>>    start using, and distribute, proliferate. And these communities produce the
>>    most software. As you pointed out, some of the software itself is free and
>>    useful.
>>
>> 2. Sometimes these ecosystems (e.g. Javascript) are so volatile, bad things fall
>>    out. It is difficult to stay abreast of changes, there are security issues
>>    (e.g. tainting a very common dependency, bootstrapping issues, etc),
>>    maintenance issues, and lots of wasted effort rewriting things. Still, a
>>    large percentage of developers' time and energy goes into that ecosystem
>>    because of point one, and they create useful things.
>>
>> 3. Sometimes these ecosystems are so volatile, good things fall out. Through the
>>    lens of experience, solutions and tools are created which address the hard
>>    won lessons.
>>
>> 4. This seems to be how nature and evolution work.
>>
>> Me? I like well-ordered things that have been thoughtfully produced. But I think about number four a lot.
>
> I do too.  :-)

Think about #4, or like well-ordered things?

> My early free software experience was that of a project managed in
> typical MIT style: the Hurd; I learned a lot from that.

Have you written about this anywhere? I'd love to hear your opinions.

> In Guix, I think we’ve always tried from Day 1 to do the Right Thing,
> but also from Day 1, we’ve always tried not to go too far and to “cut
> corners” when doing the Right Thing would have jeopardized practicality.
>
> The package simplification work that landed this summer in
> ‘core-updates’ is an example of a case where the Right Thing was delayed
> for several years because it just wasn’t attainable in a timely fashion
> back then.

I have been trying to follow the project more closely for the past few months, but I have completely missed this simplification work. Is there somewhere I can read about it? Scroll back through guix-patches maybe?

> Merging the “binary” npm importer IMO is one way to acknowledge that
> there’s a very concrete use case, that we’re unable to address it the
> Right Way, but that we offer a middle ground for users.

Thanks for these comments, and the maintainers' stewardship of Guix. I believe taking the middle way is usually the correct path, and I think Guix has benefited from it, and will continue to do so.

-- 
Katherine


  reply	other threads:[~2021-10-28 15:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 13:01 Adding extra package importers pinoaffe
2021-09-19 14:44 ` Maxime Devos
2021-09-23 20:28 ` Merging the “binary” NPM importer? Ludovic Courtès
2021-09-23 23:13   ` pinoaffe
2021-09-26 13:37     ` Jelle Licht
2021-09-26 21:34       ` pinoaffe
2021-09-26 22:32         ` Philip McGrath
2021-09-27  8:57           ` pinoaffe
2021-09-27 15:13             ` Katherine Cox-Buday
2021-09-28 12:37       ` Ludovic Courtès
2021-09-25  3:17   ` Christine Lemmer-Webber
2021-10-08  1:51     ` Maxim Cournoyer
2021-10-08 14:16       ` Katherine Cox-Buday
2021-10-11 10:13         ` zimoun
2021-10-11 17:12           ` pinoaffe
2021-10-12 18:21       ` Timothy Sample
2021-10-14  1:26         ` Maxim Cournoyer
2021-10-14 13:58           ` Ludovic Courtès
2021-10-14 14:54             ` Opining on "modern" development practices (was Re: Merging the “binary” NPM importer?) Katherine Cox-Buday
2021-10-21 19:39               ` Ludovic Courtès
2021-10-28 15:01                 ` Katherine Cox-Buday [this message]
2021-10-29 12:33                   ` Ludovic Courtès
2021-10-29 14:54                     ` Katherine Cox-Buday

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=87lf2d9orw.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.