Ask HN: Has any Rust developer moved to embedded device programming?
I&#x27;ve been working in embedded for 5 years and am curious how rust could solve my biggest headaches:<p>* Managing build configurations - I use CMake to build a single application for multiple hardware platforms. This is accomplished almost exclusively through linking, e.g., a single header file &quot;ble-ncp-driver.h&quot; with multiple &quot;ble-ncp-driver.cpp&quot; files for each target platform. I call this the &quot;fat driver&quot; approach which has proven to be easier to work with than creating a UART abstraction or ADC abstraction. Does rust&#x27;s package system address this?<p>* Automated device testing - fluid leaks are similar to bugs in software. They are systemic in nature and cannot be easily understood through static analysis. We spent equal time maintaining a test bench as product development.<p>* Preemptive operating systems - more trouble than they are worth. Often, devs get bogged down writing messages queues to pass items between task contexts and timing analysis requires detailed event tracing.<p>Given I don&#x27;t see teams struggle with memory ownership (easy to do if you never, ever malloc), what else can rust bring to embedded dev?