You're printing everyone's serial numbers publicly. https://console.darkbloom.dev/providers then "Security Verification" for any machine and then "Verify this device independently" -- all of this can be scraped.
In progress. We have access to an ARM-based supercomputer and are actively collaborating with scientists who have access to x86_64 systems. It will be a while before we have results to publish. We need to be diligent in our testing methodologies.
Diversity in the ecosystem, possible reduction in memory footprint, ability to discover and fix issues in upstream projects that musl-based distros don't currently package, motivation to support CUDA (and other) runtimes that explicitly target glibc, unlock possible sources of funding to pay developers to work on these areas.
The ability to audit a smaller codebase could be compelling for some sensitive environments.
There is not an urgent or immediate problem with glibc in the HPC space, per se.
No; at the moment we are in beta and this not yet available. We have been experimenting with various strategies to ensure rapid turnaround on security-related issues.
Our aim is to offer a non-glibc Linux platform for supercomputing environments. This involves a tremendous amount of work to be taken seriously and we are currently in the earliest stage of this. Follow our blog (https://blog.adelielinux.org/) for updates in this space.