Explore >> Select a destination
|
You are here 
|
antithesis.com | ||
| | | | |
matklad.github.io
|
|
| | | | | I've learned a thing I wish I didn't know. As a revenge, I am going to write it down so that you, my dear reader, also learn about this. You probably want to skip this post unless you are interested and somewhat experienced in all of Rust, NixOS, and dynamic linking. | |
| | | | |
crescentro.se
|
|
| | | | | What happens when a purely functional, deterministic, declarative package management system meets Python. | |
| | | | |
jmmv.dev
|
|
| | | | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | |
| | | | |
www.humprog.org
|
|
| | | |||
