For two decades, memory safety was treated as a discipline problem — write better C. In 2026 it is an economic and regulatory one. A survey of the 70% number, the Android CVE data that finally proved the fix, where Rust actually landed across kernels, what Carbon is really for, the regulations putting teeth behind it, and the honest decade-long path out of a hundred-billion-line C/C++ installed base.
Memory-Safety
-
Memory Safety in 2026: The CVE Data, the Regulatory Cliff, and the Long Goodbye to C -
The Story of C How a small language Dennis Ritchie evolved at Bell Labs to write one operating system on one minicomputer became the portable substrate beneath every kernel, every embedded controller, and the runtime of nearly every other language — and why the bargain that made it fast, undefined behavior, became the defining liability of the 2020s.
-
Carbon: Google's Bet on a C++ Successor A deep technical look at Carbon, Google's experimental C++ successor language — what's real, what's aspirational, the C++ interoperability story, checked generics, memory safety roadmap, and an honest assessment of whether it has any chance of succeeding.
-
V: Fast Compilation and Simple Systems Programming A technically honest deep-dive into V (Vlang) — fast compilation, autofree memory management, built-in ORM, and where this ambitious but controversial language actually delivers today.
-
Rust for Systems Programming: Ownership, Safety, and Where It Beats C/C++ A practical guide to Rust for systems programmers — the ownership and borrowing model, lifetimes, practical use cases, building a real CLI tool, and an honest look at where Rust outshines C and C++.