3 ms·
Our company builds a wearable device using an NRF5x chip, and our firmware is written in C. We are moving to Rust for our newest device, in order to run graphic
by maneesh 4y ago
Our company builds a wearable device using an NRF5x chip, and our firmware is written in C. We are moving to Rust for our newest device, in order to run graphical output and RT operations. It is looking pretty sweet!
- metalloid 4y agoAnd why not Carbon? :-)
- norman784 4y agoNot OP, also I don't know if is sarcasm or not, but Carbon is just too new, I would understand somehow if you asked about Zig, but isn't also mature enough.
- briantakita 4y ago> if you asked about Zig, but isn't also mature enough If you want maturity, use C. The nice thing about Zig is it's a "better C" with better interoperability & less complexity compared to Rust. Here's someone who has rewritten keyboard firmware from Rust to Zig. https://kevinlynagh.com/rust-zig/ https://kevinlynagh.com/rust-zig/
- proto_lambda 4y agoFrom Carbon's FAQ[1]: > Why not Rust? If you can use Rust, ignore Carbon. So that's probably one reason. [1]: https://github.com/carbon-language/carbon-lang/blob/trunk/docs/project/faq.md#why-not-rust https://github.com/carbon-language/carbon-lang/blob/trunk/do...
- supportlocal4h 4y agoSometimes it's hard to distinguish trolls from legitimate seekers of knowledge. I'd rather feed a troll than starve a student, 1. Carbon does not aim to replace C. It targets C++ devs. 2. Carbon is still just an idea. Well, more than an idea, but less than ready. 3. Carbon is meant for people who cannot move to something like Rust. They don't intend to compete in enviroments that have modern options.