From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Brett Gilio <brettg@posteo.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Next browser finally on master!
Date: Wed, 19 Dec 2018 20:03:51 +0100 [thread overview]
Message-ID: <877eg5jq3s.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87woo5mjzt.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
> I am also in favor
> of renaming SBCL-Next to something else. I know that we are using sbcl
> instead of clisp for building it, but the naming scheme seems to imply
> an SBCL library or module rather than a web browser application.
This is being discussed for stumpwm in bug #33311. It's not that simple: the
trick is that Lisp applications are bundled with bytecode and source code (see
the "lib" output).
Indeed, Common Lisp has the nice feature to make it possible for all binaries to
be connected to a REPL (e.g. with SLIME) and to be hacked "live"! For this to
work completely, we need to embed the source code.
Regarding the bytecode, well, it's like other languages: it's not mandatory, but
if it's not included or if you use a different Lisp compiler, the whole app and
all the dependencies will have to be rebuilt.
Currently, the lisp built-system is made in such a way that Lisp applications
always include the bytecode, which effectively bounds them to the compiler that
was used (here SBCL).
Does that make sense?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-12-19 19:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:34 Next browser finally on master! Pierre Neidhardt
2018-12-05 14:40 ` Benjamin Slade
2018-12-05 16:13 ` Pierre Neidhardt
2018-12-06 0:15 ` swedebugia
2018-12-06 8:31 ` Pierre Neidhardt
2018-12-06 9:38 ` Andreas Enge
2018-12-06 14:03 ` Pierre Neidhardt
2018-12-06 18:23 ` Andreas Enge
2018-12-06 18:24 ` Pierre Neidhardt
2018-12-06 18:29 ` Pierre Neidhardt
2018-12-06 21:02 ` Pierre Neidhardt
2018-12-09 16:19 ` Pierre Neidhardt
2018-12-09 16:21 ` Pierre Neidhardt
2018-12-19 13:40 ` Ludovic Courtès
2018-12-19 14:37 ` Pierre Neidhardt
2018-12-19 13:37 ` Ludovic Courtès
2018-12-11 7:18 ` swedebugia
2018-12-11 7:46 ` Pierre Neidhardt
2018-12-11 8:13 ` swedebugia
2018-12-11 17:11 ` Pierre Neidhardt
2018-12-19 13:35 ` Ludovic Courtès
2018-12-19 18:47 ` Brett Gilio
2018-12-19 19:03 ` Pierre Neidhardt [this message]
2018-12-19 19:08 ` Pierre Neidhardt
2018-12-19 20:32 ` Brett Gilio
2018-12-19 20:29 ` Ricardo Wurmus
2018-12-19 20:34 ` Brett Gilio
2018-12-19 21:32 ` Pierre Neidhardt
2018-12-19 21:45 ` Ricardo Wurmus
2018-12-19 21:48 ` Brett Gilio
2018-12-19 22:07 ` Pierre Neidhardt
2018-12-19 21:45 ` Brett Gilio
2019-01-03 4:32 ` Andy Patterson
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=877eg5jq3s.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=brettg@posteo.net \
--cc=help-guix@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.