unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Opining on "modern" development practices (was Re: Merging the “binary” NPM importer?)
Date: Fri, 29 Oct 2021 14:33:22 +0200	[thread overview]
Message-ID: <87y26c104t.fsf@gnu.org> (raw)
In-Reply-To: <87lf2d9orw.fsf@gmail.com> (Katherine Cox-Buday's message of "Thu, 28 Oct 2021 10:01:39 -0500")

Hi,

Katherine Cox-Buday <cox.katherine.e@gmail.com> skribis:

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

[...]

>>> 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?

Both.

>> 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.

Nope!  You’ve probably noticed that the Hurd isn’t known as a lively and
successful project, and then there are things like the Critique¹ or work
on porting the Hurd to the L4 microkernel which, while showing the
“right” direction research-wise, have also had IMO the effect of
suggesting that it’s never going to be good enough.

I think a project needs to be aware of its shortcomings, but it also
needs achievable milestones, and it needs to refrain from elitism.

¹ http://walfield.org/papers/200707-walfield-critique-of-the-GNU-Hurd.pdf

>> 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?

See <https://issues.guix.gnu.org/49169>.

Thanks,
Ludo’.


  reply	other threads:[~2021-10-29 12:35 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
2021-10-29 12:33                   ` Ludovic Courtès [this message]
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

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