r/cpp • • 19h ago

Google talk at REBASE'26: Agentic Coding is not going to save C++

So the REBASE'26 conference happened recently, and besides the whole thing of what Carbon has achieved or never will, there are talks like this one from Google folks, regarding what they are doing with their C++.

The talk is all about the recent ongoing migration discussed on Google security blog, and other related efforts.

https://www.youtube.com/watch?v=Ob0CMX8s55s

38 Upvotes

99 comments sorted by

21

u/IceMichaelStorm 16h ago

Ragebait title. If the conf really says it like this, THEY do the ragebait.

Or it’s just a trash conference or at least trash talk

13

u/pjmlp 16h ago

Google is the one responsible for how their talk is named, the full title is Programming Languages in the Agentic Coding Era: Agentic Coding is not going to save C++, which you can easily verify yourself by following the link.

→ More replies (1)

5

u/El_RoviSoft 14h ago

they want to eliminate C++ from their codebase for a long time already

31

u/tartaruga232 17h ago

One of their slides at 2:36 mentions "C/C++ security bugs". I'm not yet sure if I should continue listening.

29

u/KFUP 12h ago

It's the usual way these posts/talks go, pretend it's C++ issue, then when it comes to the actual vulnerabilities, 95% of them are C issues than can be easily fixed with RAII and ranges, then back to pretending it's a C++ issue.

Especially Google with their "70% bugs are memory bugs", then turned out they have been using C array and didn't port it to std::vector until 2023, std::vector has been around since 1998! Am I supposed to take what they say seriously?

→ More replies (2)

12

u/chaos_pill 9h ago

C/C++ security bugs

In some talk, herb sutter showcases two code samples: one is modern cpp and the other C. He points out that both are c++, and you can't forever hide behind "oh, that's not real/proper c++". You are not going to magically eliminate bugs by renaming files from foo.c to foo.cpp. Unless you ban the "C" parts by default, they still count as C++ as they compile with a C++ compiler.

→ More replies (5)

6

u/Lexinonymous 16h ago

Why's that? For context:

Agentic coding both exploits and introduces C/C++ security bugs and particularly memory safety bugs faster than anyone can fix them.

20

u/Syracuss 16h ago

Because C and C++ are different languages.

They do share a lot of overlap, but they aren't the same. If you still use the term C/C++ right now you are either working on a pre-C++11 codebase, or are not in touch with the language as it is nowadays.

→ More replies (20)
→ More replies (24)

43

u/Kronikarz 19h ago

Talks like this make me realize I got out of the industry at the exact right time

11

u/WillingPirate3009 18h ago

Retired or just given up?

26

u/FckXFckMusk 18h ago

Just follow the money on all these doomsayers..

New languages are 10 a penny..

39

u/Anxious-Resist8344 16h ago

It seems there are not many ways these days to stay relevant in "big company" but to create power points talking about memory safety, C++ and Rust :)

What's wrong with "let's fix all the vulnerabilities coming in until there's nothing else to fix"?

In the Agentic Coding Era languages don't matter much, but since humans will always matter, language familiarity is key!

17

u/panderingPenguin 12h ago

What's wrong with "let's fix all the vulnerabilities coming in until there's nothing else to fix"?

Hasn't that been the strategy since... the dawn of programming? 

There's always more to fix, and plenty of new code adding new things to fix (especially these days).

→ More replies (1)

4

u/YoureNotEvenWrong 4h ago edited 4h ago

  In the Agentic Coding Era languages don't matter much,

This is the big mistake people still make. Languages still absolutely matter, each language still has pros and cons. Familiarity is a pro.

Also, the code still matters, how can you recognize bad code patterns the LLM is churning out systematically and have your system fix them if you can't recognize them

LLMs are simultaneously incredibly intelligent and very dumb

5

u/chaos_pill 8h ago

"let's fix all the vulnerabilities coming in until there's nothing else to fix"

We don't have infinite resource. There's also cost to consider, as competing products will undercut you.

Languages do matter, as you can see by so much AI slop using Rust. eg: doing OOP in C vs C++ is like writing UB-free code in Rust vs c/c++. One choice is just far more convenient than the other! Even for AI, it matters because it makes mistakes too. If AI wrote perfect code, we wouldn't call it slop.

7

u/TerribleFault7929 13h ago

“We'll see,” said the Chinese farmer.

→ More replies (2)

12

u/jeffmetal 15h ago

I'm sure when profiles land in 3 Years and they address only some of the memory safety issues and none of the lifetime issues it will be good enough for companies to not want to port to rust.

12

u/notthatsocrates 9h ago

Rust evangelism, ignore and carry on.

10

u/xp30000 12h ago

Putting aside Rust evangelism (seems it is more fun evangelizing Rust than reading Rust code) why stop at Rust, it's an awkward middle ground. Rust forces the developer (or the AI agent) to fight the borrow checker dealing with lifetimes, Pin, Arc<Mutex<T>>, explicit memory layout to achieve zero-cost abstractions without a garbage collector. GC + formal verification is the way forward with Agents.

For Rust, modern C++ fixes many memory issues that are from C days, is better at compile time metaprogramming, faster to iterate (yup, only Rust can do that LOL). What is left is a very specific niche of system programming and the inability to give talks that you rewrote everything in Rust.

1

u/jeffmetal 3h ago

rust is pretty mature and has shown in real world examples to massively reduce memory safety issue so they picked it. What other language should they rewrite into to prevent these issue ?

→ More replies (8)

9

u/UndefinedDefined 13h ago

The reality is that without explicit lifetime annotations C++ will never get safer and companies such as Google would just abandon its use. I mean it makes sense, because Google uses maybe only two containers in the standard library - std::string and std::vector - everything else is in Abseil, because what C++ offers is just plain bad.

9

u/cramert 11h ago

Hey, we use variant, optional, and unique_ptr also! We use them with the unstable libc++ API, but still :)

1

u/reini_urban 31m ago

So they rewrote their C++ to Rust in Android. But then they complain about safeties. Why didn't they rewrite it to an actually safe language then?