unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Distopico <distopico@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Pinned/fixed versions should be a requirement.
Date: Sun, 10 Sep 2023 07:51:07 +0200	[thread overview]
Message-ID: <70b4a86b71a7c930b1446447219e037c6d023f6b.camel@gmail.com> (raw)
In-Reply-To: <87bkea23ya.fsf@riseup.net>

Am Samstag, dem 09.09.2023 um 20:37 -0500 schrieb Distopico:
> 
> On 2023-09-10, Liliana Marie Prikler <liliana.prikler@gmail.com>
> wrote:
> > 
> > [bunch of stuff regarding Rust]
> 
> 
> Beyond Rust, an example of a language/packages ecosystem that does
> not follow semantic versioning at all is JavaScript/Npm. Most
> packages in node-xyz[1] do not reference a version; they simply use
> the global input. For now, the number of npm/node packages is small,
> but with time, that could become a problem.
I don't think that pinning versions is going to help us much in the npm
case.  The node packaging model allows inputs to be propagated beyond
reason.  And the response of those gazing into the abyss for any longer
than two seconds is quite often "fuck it, I'm out" [1].  I don't think
we'll get far in packaging node stuff without solving the more
fundamental issue of "how can I replace this JS file with this JS file
and not have my entire tower of dependencies break down?" and that is a
social issue as much as it is a technical one.

Cheers

[1] https://dustycloud.org/blog/javascript-packaging-dystopia/


  reply	other threads:[~2023-09-10  5:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  2:59 Pinned/fixed versions should be a requirement Distopico
2023-09-05 17:15 ` wolf
2023-09-07 12:39 ` Pinned " Simon Tournier
2023-09-07 15:35   ` Distopico
2023-09-09 10:39     ` Simon Tournier
2023-09-09 22:50 ` Pinned/fixed " Attila Lendvai
2023-09-09 23:30 ` Liliana Marie Prikler
2023-09-10  1:37   ` Distopico
2023-09-10  5:51     ` Liliana Marie Prikler [this message]
2023-09-27  7:51 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.

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=70b4a86b71a7c930b1446447219e037c6d023f6b.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=distopico@riseup.net \
    --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).