Notices by Ludovic Courtès (civodul@toot.aquilenet.fr), page 2

Guix-Jupyter 0.3.0 released!
https://hpc.guix.info/blog/2024/11/guix-jupyter-0.3.0-released/

This is a long-overdue release of the one Jupyter kernel that can deploy the execution environment of notebooks in a reproducible fashion.

The release announcement comes with a call for help: the project needs you!

#Guix #Jupyter #Guile

Look, maybe you 🫵 can join the fabulous German, Romanian, Swedish, and Ukranian translators who already translated 100% of the messages found in 1.0.0rc1!

One nice way to contribute to the upcoming 🐑 #Shepherd 1.0.0 release is by translating it into your native language or favorite constructed language 👇
https://translationproject.org/domain/shepherd.html

#l10n #FreeSoftware #Guix

@zimoun I think that’s a good idea, but I wonder about the extent to which it’s applicable: while there’s a couple of clearly identified consistent package collections (CRAN/Bioconducator, TeX Live, Stackage), other packages either belong to inconsistent collections (like PyPI) or to no collection (the vast body of C/C++ packages).

@abcdw

@abcdw They do a better job, except when the committer is required to sign commits, as is the case in Guix; in that case the forge still leaves it up to the committer to perform the last actions.

@janneke Wo0t!! 🎉

@janneke Amazing!! Let’s hope the remaining hurd·les quickly vanish.

What better time than a week-end to try out the first 🐑 #Shepherd 1.0.0 release candidate?
https://lists.gnu.org/archive/html/guix-devel/2024-11/msg00114.html

I love the simplicity, conciseness, and clarity of this governance document by @pintoch:
https://codeberg.org/mergiraf/mergiraf/src/branch/main/GOVERNANCE.md

@nobody @zimoun At a fundamental level, this amounts to treating software packages (human-built artifacts) as if they were black boxes, natural artifacts that can only be observed through empirical methods.

@zimoun @nobody The discussion makes me think about the yin/yang analysis @khinsen published.

We have reached the point where one can say “hey, there’s a machine trying to compose packages at random for us” without risk of being criticized.

To me, this is fueling uncritical dynamics where it’s become normal to favor the “yang” (getting things done, and quickly) over the “yin” (improving our understanding of things). This is happening in academia, but really for all things software-related.

@nobody For merge trains, I’d rather look at graph theory and the literature on task scheduling than follow the trend of having a probabilistic and computationally intensive hack.

Lately I've felt a lot of "big feelings” — pain, yearning, confusion, frustration, desire — about computer programming.

I can't quite explain how I feel. Certainly can't write it down. Most definitely not in brief.

So I did the only thing that comes naturally: felt my way through it, out loud, exploratively.

Titles are hard, so it's called "Live as in Alive”, perhaps glancing sideways at the recent d-d-discourse about live programming vs live coding.

#40 —> https://ivanish.ca/hest-podcast/

“In this paper, we propose a methodology that uses historical build results to assist a package manager in selecting the best versions of package dependencies with an aim to improve the likelihood of a successful build.”
https://sc24.conference-program.com/presentation/?id=pap175&sess=sess390
https://www.osti.gov/servlets/purl/2223030

What about providing packages that successfully build in the first place? 🤔

@MonniauxD Pour être tout-à-fait à l’avant-garde, faut leur parler Guix pour les compilations reproductibles et pour l’intégration continue. :-)

Good #Guix + #HPC time today, with 25 folks on-site and 20ish on-line.
https://hpc.guix.info/events/2024/workshop/program/

One “regret” (right word?): that the attendance was +/- sold already.

But excited to see so much enthusiasm: people doing unbelievable things I’d barely dare try (incl. deploying cluster infra on Guix System), young engineers/PhD candidates “getting it” and pushing the tool to its limits, and senior folks pushing hard for reproducible deployment.

@mc Well, /bin/sh is meant to be a POSIX-compliant shell; choose whichever you prefer, as long as it’s POSIX-compliant. :-)

@luis_felipe Often there’s a “page break” (^L) right before those headings and Emacs lets you move to the next/previous page with ‘C-x ]’ and ‘C-x [’. (Not exactly what you’re asking for, but handy.)

📣 Bonne nouvelle ! Vous pourrez suivre demain la journée #Guix #HPC en ligne sur BigBlueButton 👇
https://hpc.guix.info/events/2024/workshop/program/

#RechercheReproductible #ScienceOuverte

Today my colleague Emmanuel presented #Guix to a die-hard #HPC audience—dense but energizing!
https://jcad2024.sciencesconf.org/data/PRESENTATION_Reconciling_High_Performance_Computing_AGULLO_EMMANUEL_2_.pdf

Includes an experience report moving from CMake hacks to Spack to Guix, plots showing that no, MPI isn’t any slower than vendor-provided binaries (why would it?), and long ‘guix shell’ command lines. :-)