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.
Cpp
-
Memory Safety in 2026: The CVE Data, the Regulatory Cliff, and the Long Goodbye to C -
Modern C++ (C++20/23) A dense technical tour of C++20 and C++23 — concepts, ranges, coroutines, modules, std::expected, and an honest accounting of where the language excels and where Rust wins.
-
OpenMP: Threading Without Pthreads (And Without the Nightmares) OpenMP as the sane way to parallelize C, C++, and Fortran — pragmas instead of pthread plumbing for parallel loops, tasks, and GPU offload — plus the data-sharing and scheduling details that decide whether you get speedup or bugs.
-
Verilator Deep Dive: Open-Source Simulation That Can Actually Replace Your Commercial Tool Modern Verilator as a genuine alternative to commercial RTL simulators — compiling SystemVerilog to cycle-accurate C++ that runs 10-100x faster — covering what it now handles well, its limits, and how to wire up testbenches.
-
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.