News for hackers. Stuff that matters.
Re:Things you can’t do in Rust (and what to do instead) by jvanderbot on Saturday May 15, 2021 @04:04PM (#27168497)
Long time C++ user here.

Precisely right (for me!): It is easier to get to compile because it is easier for me to express and easier to debug type / syntax problems. Once compiled, it has a very high probability of just working.

I'll add that the exercise of learning rust has distilled the lessons learned in writing "good" C and C++ into a language that has few other ways of doing things. It's like someone is guiding me through good multi-threaded, memory management, and type design practices in C++ every time I work on a Rust project.

This experience absolutely translates back when I'm working on C++ and C.

Rust has huge potential it it can keep its libraries "upstream" of other languages. C is king of providing a one-implementation-to-many-languages (though API wrapping). If Rust can accomplish that, it'll be my language of choice. As much as I love the Unix philosophy of many interacting programs, the reality is for most systems that dynamic or static linking is how things interact.

There are no comments on this comment yet.