We've just published the Guix-HPC annual report!

👉 https://hpc.guix.info/blog/2022/02/guix-hpc-activity-report-2021/

See how we support #ReproducibleResearch workflows, from core #Guix work to #SoftwareHeritage support to #Jupyter integration and more.

Reason I mention this is that while hunting a bug involving Python in a relocatable pack produced by ‘guix pack’, we found that Python provides ‘os.path.normpath’, which is documented as doing the “wrong” thing—that is, “lexical” dot-dot resolution instead of what POSIX expects:
https://docs.python.org/3.11/library/os.path.html#os.path.normpath

@CodingItWrong I don’t know of any language-specific curated repo: they all seem to favor rapid growth and developer-friendliness over user-friendliness. Traditional free distros are curated, though.

Non-copyleft licenses are the norm in Rust. Nothing prevents you from choosing a copyleft license, but making that choice “excludes” you from the Rust community and there’s a strong incentive to follow the norm (e.g., see how Sequoia recently dropped its weak copyleft license.)

@CodingItWrong It excludes you in the sense that other Rust developers will say they “can’t” use your code because it has the “wrong” license.

It’s just social pressure, nobody is formally excluding anyone of course.

#Rust seems to have grown an individualist community, with all its tiny packages hosted in a non-curated repo, with its rejection of copyleft, and with its disregard of #FreeSoftware “community standards” developed by distro folks over the years.

I feel that introducing Rust right into once collectively-developed code bases at the core of GNU/Linux will have unpredictable and detrimental effects.