DEV Community

Asael Shinder
Asael Shinder

Posted on

More of the New Code Around You Will Be Written in Memory Safe Languages

For decades, a large part of the software the world runs on has been written in C and C++. Those languages are fast and flexible, and they let the programmer manage memory directly. They also make it easy to make mistakes, such as reading past the end of a buffer or using memory after it has been freed. Those mistakes are a major source of security vulnerabilities.

The numbers are striking. Microsoft and the Chromium project have each said that roughly seventy percent of their serious security bugs come from memory safety problems. Google has reported that as Android wrote more new code in memory safe languages, the share of its vulnerabilities caused by memory safety fell from about three quarters in 2019 to about a quarter in 2024.

Governments have noticed. In the United States, CISA and the FBI have published guidance telling software makers that products written in memory unsafe languages should have a published plan for reducing that risk, with January 2026 named as the date to have one. Other agencies around the world have issued similar advice.

The direction is clear. More new projects will be started in languages such as Rust, Go, Java, C sharp, Swift and Python, where the language or its runtime manages memory for you. Rust gets most of the attention because it offers memory safety without a garbage collector, which matters for operating systems, browsers and devices. It is already used in parts of the Linux kernel, Android and Windows.

What does that mean for you?

If you already write in a memory safe language, the most useful thing is to understand why it matters. Customers and security teams will increasingly ask about it, and you should be able to explain it in plain words.

If you work in C or C++, nobody is going to rewrite everything soon. Huge amounts of existing code will be maintained for many years. But new components may well be written differently, and the people who can work comfortably across the boundary between old and new code will be very valuable.

And if you are choosing what to learn next, a few weekends with Rust are a good investment. Even if you never use it at work, it changes how you think about who owns a piece of memory, and when.

– Asael Shinder

Top comments (0)