The hardware answer to the problem eBPF and WASM solve in software: a pointer that carries its own bounds and permissions, enforced in silicon. Still an unratified RISC-V extension, whatever the coverage implies.
Two years of government documents ask vendors to stop writing new code in memory-unsafe languages and to publish roadmaps for the old code. None of it is law. The clearest production-scale evidence yet that the roadmap approach works arrived last month: five years of Android results, published by the vendor rather than demanded by a regulator.
Memory safety without a garbage collector was a research position for thirty years. What changed wasn't the idea; it was a toolchain good enough that people ship with it.
