Mitigating Memory Safety Issues in Open Source Software

Re:Mitigating Memory Safety Issues in Open Source Software by cameronhowe on Thursday February 18, 2021 @10:55AM (#26181304)

I know I'm only one person, but I'm a C programmer at my day job and I do all my hobby projects in Rust.

For me cargo, rust-analyzer, and lifetimes/borrow checker just makes programming so much more pleasant.

edit: I dont go overboard on the more advanced features in the rust language, and probably write more C idiomatic code sometimes, but I still prefer using rust over C

[ Parent | on HN ]

Re:Mitigating Memory Safety Issues in Open Source Software by ragnese on Thursday February 18, 2021 @11:32AM (#26181897)

For sure. I didn't mean to suggest that nobody from C land would enjoy Rust. Just that I think the trend will be that more C++ people move to Rust than C people.

But my point of view is quite biased. I am still baffled that people would start new projects in C instead of just using a strict subset of C++, at least: classes, only trivial templates for generics, references, maybe smart pointers depending on what you're doing, but no STL, no exceptions, no inheritance, etc.

[ Parent | on HN ]