Hello! New Rust learner here. Need help with direction about the realities of embedded with Rust.

Embedded is/was my first love, in technology, ever since my electronics engineering degree project decades ago. I did an embedded project then with 8051, but nothing on that until now. Currently I am a senior developer with experience in web applications / cloud / some distributed systems with C# / aspnetcore ecosystem.

My primary motivation is learn the language better, build same things like I did earlier but with more understanding, skill, and enthusiasm than I ever did with C#. To realize this, I set out on this path: RBE->The Book->Rustlings->build a few production grade showcase projects->go deeper into distsys->then embedded and electronics. Currently I am in the middle of RBE.

My eventual goal is to make real world products in a few years. So thought I'd start on Embedded Discovery book, and then STM32 book and so on.

However, earlier today I was researching about embedded with Rust and came to the conclusion that learning C is inevitable. This I put together from the fact that the CS:APP book introduces us to the hardware side of memory, processes, assembly, etc. This book has C code for all of that. This means I need to take another detour with a book (Modern C, KN King). I am not getting any younger to have so many detours.

Is this unfounded and I can just continue with the prescribed paths or what I found is real and a Learning C detour is a necessary frog to swallow?

Thank you,
danmsh.

6 posts - 2 participants

Read full topic