5 ms·

I think one can both be excited about Rust and acknowledge that for most projects C is still the way to go. The libraries, communities, compilers, vendor suppo

by fra 7y ago

I think one can both be excited about Rust and acknowledge that for most projects C is still the way to go. The libraries, communities, compilers, vendor support, ...etc. is much more mature on the C side of things and will remain that way for a while. At the same time, Rust is getting to the point where early adopters can start using it for their projects. Those are the people who will make Rust a full class option in the future.

zozbot234 7y ago
Rust can interoperate with C libraries, it's a pretty substantial part of its value proposition. At the same time, it's true that C has way better compiler support for weird embedded targets, and it's also a comparatively mature language that's not going to change much over the years, with a vendor-independent standard definition. For some projects, these things might be important.
- adwn 7y ago
  > Rust can interoperate with C libraries True, but speaking as an embedded developer and Rust fan: embedded C libraries just love their #defines in public APIs. This makes interfacing with them from anything but C or C++ more cumbersome, because you can't just declare "extern" functions, you also have to translate the #define macros, which are sometimes non-trivial.