Memory Safe Languages in Android 13

Re:Memory Safe Languages in Android 13 by logicchains on Thursday December 01, 2022 @11:08PM (#33826657)

>If they’re saying that C++ can’t be saved, maybe they’re worth listening to.

Google's one of the worst C++ shops because their code standard basically forbids using modern C++, and their C++ is more like 90s Java than modern C++. It's no wonder they want to get away from it.

[ Parent | on HN ]

Re:Memory Safe Languages in Android 13 by Xorlev on Thursday December 01, 2022 @11:31PM (#33826806)

I...what?

I write C++ at Google, and it encourages use of modern C++ features, and many things you see adopted in std have roots in our libraries.

I'm curious what you think Google prevents us from using and why you think our C++ is like 90s Java.

https://abseil.io/tips has a lot of our philosophies and abseil is chunks of our internal libraries published externally.

[ Parent | on HN ]

Re:Memory Safe Languages in Android 13 by UncleMeat on Friday December 02, 2022 @08:28AM (#33830157)

I've weirdly heard people say this in the past too and I am equally baffled.

I think it stems from the fact that Google was slow at making C++11 available internally so there was a period of time where the rest of the world was using smart pointers and we couldn't. That may have just solidified a "Google uses old C++" meme out in the wild despite it being wildly out of date.

[ Parent | on HN ]