this post was submitted on 07 Sep 2024
30 points (94.1% liked)

Tech

457 readers
9 users here now

A community for high quality news and discussion around technological advancements and changes

Things that fit:

Things that don't fit

Community Wiki

founded 8 months ago
MODERATORS
top 6 comments
sorted by: hot top controversial new old
[–] jqubed@lemmy.world 10 points 2 months ago

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.

[–] kersplomp@programming.dev 9 points 2 months ago

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..."

[–] FizzyOrange@programming.dev 7 points 2 months ago

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.

[–] refalo@programming.dev 5 points 2 months ago* (last edited 2 months ago) (1 children)

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

[–] Taleya@aussie.zone 4 points 2 months ago

Maybe but at this point any thing google suggests is a signpost to do the opposite