2 ms·
That's ecosystem maturity problems. Regardless, your first mistake was not immediately reaching for linking to the C libs from Rust, which is something the lang
by packetlost 4y ago
That's ecosystem maturity problems. Regardless, your first mistake was not immediately reaching for linking to the C libs from Rust, which is something the language is designed to do rather easily.
- kjetijor 4y agoFor matter/thread you'll likely even have to go the other way around - link to your thing written in rust from your matter/thread project. And yes - this is partially a maturity thing, although more in the sense in that the embedded ecosystem is very vendor specific, and you're traveling outside the path the vendor forged for you, so you'll be an early trailblazer - you get to deal with all the integration shit, rather than finding some other random person on the internet that's dealt with something similar. (And it's not necessarily that the vendors path is all that great, but at least there's a whole collection of other people that's struggled with it and posted about it online). Our professor in college was livid when we suggested not using the vendors toolchain (back in the early 2000's), "yes $vendor's toolchain is broken and shit, but it's marginally less broken and shit than $non-vendor toolchain".