Given last week’s stories about Rust and the Linux kernel, this almost feels like a pointed message from Google’s devs to the Linux kernel devs.
Tech
A community for high quality news and discussion around technological advancements and changes
Things that fit:
- New tech releases
- Major tech changes
- Major milestones for tech
- Major tech news such as data breaches, discontinuation
Things that don't fit
- Minor app updates
- Government legislation
- Company news
- Opinion pieces
Nit: One engineer at a company saying something is not the same as that whole company saying something. I wish they would just say "Google employee insists..."
Make sense. Firmware is also extra difficult to debug so it's nice to use a language that significantly reduces the amount of debugging you need to do.
Maybe but at this point any thing google suggests is a signpost to do the opposite
I want to see specific examples of serious bugs that rust would catch that clang -Weverything
, clazy/clang-tidy
and scan-build
would not find for C++... because I'm still not convinced it is anywhere near worth learning at all for career/veteran C and C++ folks.
This isn't a complete answer to the question you asked, but it could be: https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html