From: Maxime Devos <maximedevos@telenet.be>
To: Ryan Prior <rprior@protonmail.com>, jgart <jgart@dismail.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: developing javascript with guix
Date: Sat, 30 Jul 2022 21:50:19 +0200 [thread overview]
Message-ID: <74bbf79c-6cfe-fc1b-2aaa-83692364a36a@telenet.be> (raw)
In-Reply-To: <7K0vjV4NvEKb0D-wEmmFrZrnJIJRCzAAPhxOe0b4qRqr10cYam8bO2M2mgiQcBD5tO08B7NqFBo_xn-LCDzg-sS_VKdzVhm4_cwpceZyi60=@protonmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 779 bytes --]
On 28-07-2022 01:15, Ryan Prior wrote:
> Is there really a use case for shipping the source code of a JavaScript library without the interpreter?
Yes -- see "guix build --source" (it's not JavaScript-specific).
If you meant the _compiled_ JavaScript library (result of "guix build
node-...") (even when it's maybe just copying source code around and
maybe minimisation), then also yes:
JavaScript isn't only used in node, but also on the web, in browsers.
While not all node-based libraries are usable on the web, I'd assume
some of them are. So it would be nice if "guix shell -D
the-web-server-app-thing" didn't install the node interpreter you didn't
ask for (functional package management) and don't need (resource savings).
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-30 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 0:25 developing javascript with guix jgart
2022-07-27 9:33 ` Maxime Devos
2022-07-27 22:25 ` jgart
2022-07-27 23:15 ` Ryan Prior
2022-07-30 13:40 ` Luis Felipe
2022-07-30 16:04 ` bokr
2022-08-03 14:26 ` david larsson
2022-07-30 19:36 ` Maxime Devos
2022-07-30 19:44 ` Maxime Devos
2022-07-30 19:50 ` Maxime Devos [this message]
2022-07-30 20:22 ` Maxime Devos
2022-08-03 13:18 ` Giovanni Biscuolo
2022-07-30 19:35 ` Maxime Devos
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=74bbf79c-6cfe-fc1b-2aaa-83692364a36a@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--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 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.