I was able to catch it and even reproduce it this time!

A NULL pointer dereference… 🤦‍♂️

Again, dear programmers, please use #Rust and stop using (old) languages with very old problems.

No, it is not a skill issue. Look at statistics.

Today, using something like #C and #Cpp when you are able to use #RustLang means at least to me that you don't give a fuck about your users and their security.

BTW, "new" is not always better as #GoLang shows with its nil 🤦‍♂️

#FlipperZero

Reply to this note

Please Login to reply.

Discussion

nostr:npub129gvast08lj986yftn7q5qlnj8yfqufxx0m33s9u5xssjm8c64rsve4kwg I’m an avid Rust evangelist, and I use a lot of Rust in embedded dev, but this is a dumb hot take.

Programming languages are tools. There are tools for different jobs. In Rust, you could have an unwrap which panics instead of a nullptr deref in C. Both are a skill or tooling or testing methodology issue.

Please don’t taint Rust with this mindless drivel. Be better than this.

Well said, thank you.