Moving from C to Rust for embedded software development 

ive been thinking this for a while now too! honestly shocked to see this channel at less than 400 subs

I can't speak for The Rusty Bits, but I wonder how many of them are from talented developers being laid off.

Wow, no kidding…. subscribed, hoping for more!

people caring about end quality and editing instead of just uploading. plus with all the tips/tricks on how to make a youtube channel good (the video is barely over the 10 minute mark).

They have been! Some just got better at editing. Others got finally blessed by the algorithm. It's long overdue!

You're commenting on the video's humorous portrayal of the IMU sensor as the "ears" of the operation -- which very accurately corresponds to vestibular system of our inner ear, and its ability to sense linear and rotational acceleration!

Word! (Came to the comments section just to say exactly the same)

RP2040 and ESP32 projects would be awesome! I want to see if I can move away from the arduino framework.

I was laughing hard! 😂😂😂 kept face palming internally knowing I found these funny it gave me insight into the realm of my actual sense of humor 👌🤣

This is actually the biggest thing thar puts me off apart from the syntax visually feeling worse than even c++.

​@@BeefIngotI found AI tools really useful for helping understand the syntax and error messages. I'm using Codeium right now, it seems as good as copilot but free to use.

​​@@BeefIngotimo give the rust book a read instead of relying on ai, and sure it goes over the complete basics but that way everything just makes sense as you go deeper

Thanks! Embedded systems can be a lot of fun, pointer issues notwithstanding 😅 The music is all from Epidemic Sound.

Thanks! 😂 We've still got that 'new channel smell', so the algorithm is still figuring out what to make of us, but we've got high hopes!

Rust does help with this. I’ve been programming for like 25 years and I honestly feel so much less anxiety that something is going to go very wrong with Rust. Don’t get me wrong, you can absolutely still make logic mistakes, but it’s usually much more straightforward to see what went wrong. What does get a bit frustrating is when you’re pretty sure you’ve got things right but the compiler’s telling you you’re screwing it up but you just can’t figure out what the right way to do things is. And here’s the thing: if you’re not in a hot loop: copying to fix an issue can usually get you out of a jam. YMMV as you get aim for lower and lower hardware specs.

Yes, some DIY with Embassy and like the S3 series microcontroller would be great!

Just to clear things up in case it was not a typo, GPS messages are in NMEA format and NEMA is a standards organization like ISO or IEC :)

On another note, as a beginner would you say doing something with medium complexity is easier or harder in C compared to rust? I could imagine learning pointers and memory management from scratch would be just as hard as learning how to overcome the borrow checker🤔

@@amos9274 For medium or high complexity work the borrow checker shouldn't get in the way as much as it benefits you by preventing broken architectures. I'd say if you care about it actually working reliably you're better off using Rust instead of C. (35 year C veteran, 2 year Rust intermediate here.)

@@amos9274Manual memory management, is not that hard. What makes working with C so much harder than it needs to be is that because of it's origin and history, most C compilers simply assume you are a god at programming and trust you 100%. In fact they trust you so much that they will optimize your code as is. Which is fine to do when you have as much Words of memory than my comments has, but this is excruciating to work with. C type system is inexistant, the compiler won't enforce anything without you adding 3 billions of weird platform specific, compiler specific, poorly documented, cryptic named flags, that still let you do stupid stuff. Really for any project go with Rust, I'm not big on it I prefer Zig but the point is anything at this point is better and more ergonomic than C.