As someone who has worked as a professional Clojure programmer, I would
like to add my voice in support of this:
On Mon, Feb 19 2024, Ryan Sundberg wrote:
> ... In my experience using AOT is the exception rather than the rule;
> it is a nice optimization when practical for release engineering, but
Hi Guix,
I have a little i686-linux laptop to which I deployed the Sugar desktop.
The only user account on that laptop (other than root) has no Guix
profile.
I switched to that user account and ran “guix package -d”. Here is what
happened:
--8<---cut here---start
As a daily Clojure programmer using Guix the default 'off' makes sense. The
only situation where AOT compilation is useful is in the final runnable
application programs, and even then, its often incompatible with AOT
compilation in subtle ways. Having libraries aot compiled not only adds
incomp
((As I said about a month ago, in theory I should have access to a proper
e-mail program again a week or two in the past.))
>Hi,
>Guix's clojure-build-system turns on AOT compilation by default. I would like
>to advocate that 'as a distributor' we should *not* ship Clojure code AOT'd,
>so we s
Hi,
Guix's clojure-build-system turns on AOT compilation by default. I would like
to advocate that 'as a distributor' we should *not* ship Clojure code AOT'd, so
we should change the default.
This has been discussed previously. In #56604 r0man noted that AOT compilation
should not be on by def
On Fri, Feb 16, 2024 at 02:33:02AM -0600, Lilah Tascheter wrote:
> one more quick change that I've realized will be necessary: add a
> bootloader-targets field to boot-parameters. some bootloaders would
> need target info to know where to install config files, and
> reinstall-bootloader doesn't hav
