From: Yasuaki Kudo <yasu@yasuaki.com>
To: Ryan Prior <rprior@protonmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Building a software toolchain that works
Date: Thu, 17 Mar 2022 05:13:44 +0900 [thread overview]
Message-ID: <3AA4FABC-0651-4172-BC28-344E04375CD1@yasuaki.com> (raw)
In-Reply-To: <g7jNNhg5OJCBmXfXsEg3rtuHIKu2oesfKHMY9o2fqG9laMzAPYdjnYzSSakKf5NjikIUT_dTd5--XEHqTYv_8QZlY7W4qjqVFyc1I7dntD8=@protonmail.com>
I am very interested in this topic, too!
At work, I have been forced to use the NPM package manager and since the first day I have been unable to understand this enigma - how on earth do people work with this fuzzy system almost designed to be unaccountable?? Can Guix replace NPM?
I think we are really onto something - my hunch is that technicalities are only half of the issue and the other is the community building for democratic and accountable software(for which, concepts like Free Software will fit naturally)
-Yasu
> On Mar 17, 2022, at 00:29, Ryan Prior <rprior@protonmail.com> wrote:
>
> On Wednesday, March 16th, 2022 at 2:02 PM, Josselin Poiret <dev@jpoiret.xyz> wrote:
>
>> Let me chime in on a specific point.
>> [...]
>> I don't think I would've written these patches without Guix's help.
>
> This is CRUCIAL to Guix's value proposition: by abstracting away so much of the incidental complexity of software, Guix enables a nimble, carefree mode of hacking where you'll create and improve software that would never have been worth the trouble otherwise.
>
> Proposals like David's `guix contribute` play on the strength of Guix as an enabling technology. That's exactly the kind of thing I meant when I wrote "double down." How can I encourage the improvement & implementation of such proposals? A few notions:
>
> a. My Guile isn't strong enough to put together a proof-of-concept in Guix as a solo effort. I might be able to write a PoC in concert with a more experienced Guiler. We could schedule some strategy & pair programming sessions to get something on track.
>
> b. I could work on a PoC using a language I'm better trained with (elisp, Ruby and JavaScript are my three strongest languages probably.) I don't know how that would be received by the Guix commons, I've felt discouraged in the past to extend Guix unless it's in Guile but perhaps that's a false anxiety.
>
> c. I could also provide some funding if somebody has time & skills to create a PoC and just needs the financial incentive. If this is you, reach out.
>
>
> I've been pleased to see ideas resonate in this thread. It makes me believe many of us have some form of this thought in our heads and that by socializing we can bring something fresh to the free software world. What are the next steps?
>
next prev parent reply other threads:[~2022-03-16 20:14 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 [this message]
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 ` Building a software toolchain that works Katherine Cox-Buday
2022-03-18 6:27 ` 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
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=3AA4FABC-0651-4172-BC28-344E04375CD1@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=guix-devel@gnu.org \
--cc=rprior@protonmail.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).