Explore >> Select a destination
|
You are here 
|
blog.thalheim.io | ||
| | | | |
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?... | |
| | | | |
antithesis.com
|
|
| | | | | We're open-sourcing a tool that may be useful to people who develop code on NixOS and distribute it in binary form. | |
| | | | |
www.hurryupandwait.io
|
|
| | | | | ||
| | | | |
nabeelvalley.co.za
|
|
| | | Debug Node.js code using your browser's dev tools | ||
