this post was submitted on 09 Sep 2024
179 points (94.5% liked)
Programming
17351 readers
342 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Mixing "firmware" with "easy with minimal experience" in the same sentence makes me cringe...
That's fair. To be clear, I meant minimal experience with the Rust programming language. I've mainly tinkered with ESP32 types of MCUs in Arduino and CircuitPython when it comes to firmware, but have much more software experience. In some ways, I found the little bit of Rust that I tried easier because of the tooling - defaulting to a CLI tool to flash rather than an IDE is much more comfortable for me.
I've been meaning to play with rust, and I've always enjoyed tinkering with various MCUs... Although I'm not very strong with firmware/embedded programming.
Do you think programming an ESP32 is a good project for learning rust?
Any suggested place to start? (Tutorials, YouTube Vida etc)
I've only barely scratched the surface there myself but, I absolutely do think so. For several reasons. First, ESP32 is one of the few series of MCUs that support the Rust stdlib. And learning what that entails for Rust is extremely helpful in conceptualizing build targets. Second, MCUs are a very constrained target for software/firmware. Getting comfortable there will likely improve your code efficiency in other code platforms as you are more likely to think about resource usage earlier. And third, there's some pretty excellent docs and tutorials.
For tutorials, my recommended starting point is with the official docs/books themselves:
Meh, it's depends on what you do. I know several low level C engineers who would be far more comfortable rolling a fresh driver over doing some more abstract intro CS projects.