Proud to start sharing Google's strategy for tackling our remaining memory safety challenges: security.googleblog.com/2024… High level, but it outlines the long-term strategy. We'll be sharing more detailed posts in this series. #CPlusPlus #RustLang #CarbonLang

Safer with Google: Advancing Memory Safety

Posted by Alex Rebert, Security Foundations, and Chandler Carruth, Jen Engel, Andy Qin, Core Developers Error-prone interactions between ...

security.googleblog.com

Oct 15, 2024 · 6:21 PM UTC

6
12
69
Replying to @chandlerc1024
What's the benefit of Carbon over Rust?
1
2
If it works, much more comprehensive, integrated, and incremental interop and even automated migration where possible.
4
Replying to @chandlerc1024
Does Carbon have a solution for safety yet? I seem to remember it was a “safe subset” approach initially right?
1
2
Carbon is still early stages, but we're aiming to have a similar level of safety to Rust or Swift long term.
1
4
more replies
Replying to @chandlerc1024
sleeping better lately ah?
Replying to @chandlerc1024
Love to see these sequence of safer languages posts.
Replying to @chandlerc1024
I don't understand why carbon is design by committee
1
Load more