Writing in their bog, the insecurity experts have called for a  "common framework" with "specific, measurable criteria" to whip developers into shape and ensure precious memory is safe from their reckless coding.

Forget outdated tactics like code auditing, fuzzing, and exploit mitigations. Google's brain trust has declared that these methods "haven't been enough to stem the tide."

Clearly, it's time to up the ante and impose some rigorous standards to keep those pesky developers in line, the blog says.

Google's visionaries are now championing a "blueprint for a memory-safe future" where "defining the desired outcomes” is better than being locked into specific technologies.

Google is "actively working to build" this memory-safe paradise. They're collaborating with industry and academic partners to concoct potential standards and have even co-authored a recent call to action in the Communications of the ACM.

Internally, they are "prioritising memory-safe languages" like Rust, Java, Kotlin, and Go.

The blog says the moves are all about "creating a level playing field" and "empowering informed decision-making."

They call for a "collective commitment to standardisation" because everyone knows a good official standard solves everything.

 The journey towards memory safety requires a collective commitment to standardisation. We must build a future where memory safety is not an afterthought but a foundational principle. In this future, the next generation inherits a digital world that is secure by design,” the blog says.