@apxmachit Personally I use Rust as a replacement for Embedded C. I find C too difficult to teach for embedded platforms like PineTime Smart Watch.
One of the biggest issues with embedded C is with the Pointers... It's really easy write pointer code incorrectly.
With Rust we can handle objects safely without worrying about pointers. And yes I still write "unsafe" code on Rust, but at least they are flagged out for easier review.
I still prefer Embedded C for writing operating system code (like Mynewt OS). But for embedded apps that run on top of the embedded OS, I think Rust is the better choice 🙂
CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.
@apxmachit Personally I use Rust as a replacement for Embedded C. I find C too difficult to teach for embedded platforms like PineTime Smart Watch.
One of the biggest issues with embedded C is with the Pointers... It's really easy write pointer code incorrectly.
With Rust we can handle objects safely without worrying about pointers. And yes I still write "unsafe" code on Rust, but at least they are flagged out for easier review.
I still prefer Embedded C for writing operating system code (like Mynewt OS). But for embedded apps that run on top of the embedded OS, I think Rust is the better choice 🙂