C/C++ undefined behavior everywhere & AI agents build Paxos in Rust - Hacker News (May 20, 2026)

[0:37] C/C++ undefined behavior everywhere

First up, a blunt take on C and C++: undefined behavior isn’t some rare edge case—it’s everywhere. The argument is that the standards give compilers and hardware permission to assume certain “impossible” situations never happen, which means ordinary-looking code can become untrustworthy across platforms and builds. The post walks through examples that many developers have written without thinking twice—like passing the wrong kind of char into ctype helpers, relying on null pointers coming from zeroed memory, float-to-int conversions that silently step outside defined territory, or type mismatches in variadic functions such as printf-style calls. Why it matters: UB is not just academic. When untrusted input can influence an out-of-bounds read, a divide-by-zero, or a bad pointer access, correctness and security become moving targets—especially as compilers get more aggressive and environments get more diverse.

Second, the Virtual OS Museum aims to make computing history runnable, not just collectible. It packages a huge library of historical operating systems and classic applications into a single Linux-based virtual machine that works on common hypervisors, with snapshots so you can experiment and roll back when things break. The point isn’t nostalgia—it’s accessibility. When old environments become easy to boot and explore, it gets dramatically simpler to teach system design, understand compatibility constraints, and preserve software that would otherwise rot behind emulator setup pain.

One more story on governance and control in tech: Swiss cloud provider Infomaniak moved majority voting rights into a public-interest foundation designed to block takeovers permanently. It’s a structural response to consolidation pressure and geopolitical uncertainty, and it comes with a charter that commits to principles like independence, privacy, and restrictions on training AI on customer data without explicit consent. Why it matters: for organizations handling sensitive data, “who can buy your vendor” is a real risk. This is one model for baking long-term constraints into ownership—whether you love the approach or not.

Finally, a reminder that systems thinking extends beyond software. Japan’s widespread hay fever problem is being tied to postwar reforestation choices—large monocultures of cedar and cypress that now release enormous volumes of pollen into nearby cities. The response isn’t simple, because forests also stabilize slopes and store carbon, so “just cut them down” creates new problems. Why it matters: this is a case study in long-term consequences—how large-scale optimization for one goal can produce decades-later externalities, and why policy fixes often require careful, multi-objective engineering rather than a single-metric solution.