<rekado_>“and this is a significant difference compared to other buildpacks” — I get why this interjection exists, but it doesn’t actually fit, because the interjection is generic while the surrounding sentence is specific
<rekado_>obviousy, other buildpacks don’t use “guix time-machine” and “channels.scm”!
<rekado_>i think this sentence would benefit from mentioning the generic solution first before speaking of the specific (namely “guix time-machine” and “channels.scm”)
*rekado_ commented on the merge discussion on github for good measure
<rekado_>“However, there is in HPC circles the entrenched perception” — I’d reorder words a little, because I can only read “there is in HPC circles” haltingly. I’d do “However, in HPC circles there is the entrenched perception”
<rekado_>“AVX-512 on x86_64, NEON on ARMv8” – should this be “such as AVX-512 on x86_64, or NEON on ARMv8”? Or is this really a fixed tuple?
<rekado_>“We showed that these concerns are largely unfounded…” — I’d put the articles in chronological order. I was surprised to see the 2018 article mentioned after the 2019 article.
<civodul>"we deployed, on the Guix build farm, infrastructure to continuously ..."
<rekado_>“The latter article showed” <— this would need changing then, too
<rekado_>“A notorious example of packages that do not support FMV are C++ header-only libraries, such as the Eigen linear algebra library.” — this is another numbers confusion. “A notorious example”(singular) “are libraries” (plural), “such as this library” (singular)
<civodul>i like that i can learn how to improve on all this :-)
<rekado_>“Guix proposed a dozen of Julia packages” — I don’t know what “proposed” is supposed to mean in this context.
<rekado_>(and I think the “of” can be left off; with “of” it sounds to me like what follows is a commodity with a well-known unit)
<rekado_>“the built-in Julia package manager, Pkg, to find…” — better to remove the commas.
<rekado_>“and the work behind it” — this is ambiguous. On a first read it sounds like “how much work people put into the package” and not “what work the package manager performs on behalf of the user without them knowing”
<rekado_>— or maybe that’s exactly what it’s supposed to mean :)
<rekado_>“specific software on our own guix channel” — using monospace for “guix” here is a little odd. How about just “Guix channel”?
<rekado_>“the strategy holds its promise” — I think this is actually wrong
<rekado_>“hold promise” is an idiom to say that something has potential
<rekado_>“keep its promise” would be that it is indeed as good as we had hoped
<rekado_>but maybe it’s better to get rid of the whole promise thing and rewrite that sentence a little
<rekado_>that whole sentence reads a bit too much like it was brought up in a casual conversation
<rekado_>the last two sentences could perhaps be replaced with something like: “We aim to eventually replace as many of these deployed machines as possible, adjusting Guix system services and implementing new ones as we go, benefiting the wider community.”
<rekado_>on fourth thought, perhaps the Articles section is the right place after all to mention the PiGx SARS CoV2 preprint.
<rekado_>it’s not fundamentally *about* reproducibility or Guix, but *PiGx* is.
<rekado_>“GNU Guix is a collaborative effort, receiving contributions from more than 90 people every month” — does this include the extra channels?
<rekado_>should we at least mention our extra channels like guix-science, guix-bimsb, guix-hpc, etc?