If you're programming for ESP, then embassy is the way to go in most cases. You don't need to learn much about lifetimes in most of the application code. Steep learning curve people refer it is "thing blow up at compile time vs runtime." It's easy to write JS or C that passes all tests and compiles and then wonderful blows up when you start using it. It just forces you to learn things you need to know at IMO right now.
My biggest problem with rust right now is enormous target/ dirs.
Re:Ladybird Browser adopts Rust
by JoshTriplett on Monday February 23, 2026 @03:00PM
(#47127898)
> My biggest problem with rust right now is enormous target/ dirs.
We're working on that and it should get better soonish. We're working on shared caches, as well as pruning of old cached builds of dependencies that are unlikely to be reused in a future build.
thanks beejesus! (aka the devs) I'm tired of forcing shit into workspaces just to slightly mitigate these issues
Re:Ladybird Browser adopts Rust
by Foobar8568 on Tuesday February 24, 2026 @12:53AM
(#47133344)
I feel compilation time is unbearable in Rust, even on MacBook pro M3 max, don't get me started on space
I used to think that I would never write C code again, but when I decided recently to build something that would run on ESP32 chips, I realized there wasn't any good reason for me to use Rust yet. ESP-IDF is built on C and I can write C code just fine. C compiles quickly, it's a very simple language on the surface, and as long as you minimize the use of dynamic memory allocation and other pitfalls, it's reliable.