#systems-programming
Wiki 11
- ABI Stability Binary-level compatibility contracts: kernel vs glibc philosophies, Wine as the stable option
- Arena allocation Region-based memory management — allocate many objects into one buffer, hand out references or indices, free the whole region at once
- Bryan Cantrill Systems engineer, DTrace co-creator, Oxide CTO; writes on software engineering culture
- C3 Christoffer Lerno's C-tradition systems language; opinionated successor that's rethinking C's defaults from scratch
- dayvster.com Dayvi Schuster's blog — modern systems-language opinions (Zig, Odin, C3), C++ defense, memory-management primers, anti-Rust contrarian takes
- Dropping Privileges in Go A Go program self-restricting at startup — chroot, setrlimit, pledge/unveil, seccomp, Landlock — via x/sys/unix
- icefox (wiki.alopex.li) Simon Heath's personal wiki; programming-language design, systems programming, software culture
- internals-for-interns Jesús Espino's weekly blog on software internals — Go runtime, filesystems, Linux kernel — written as "useful maps" not exhaustive references
- Privilege Dropping Least privilege applied at startup — acquire resources, then irreversibly shed capabilities so a later compromise is contained
- Why manual memory management still matters Dayvi Schuster's tour of manual memory management — common pitfalls, the stack/heap mental model, and how C, Fil-C, C++, Zig, Odin, C3, and Rust each handle it
- Zig Andrew Kelley's systems language; manual memory via arenas and allocators, no hidden allocations, comptime as the type-system programming mechanism
Toolbox 1
- tc-lang (Tig) Minimalist systems language transpiling to readable C11, with fat pointers, defer and errors