Issue #81 of The Embedded Rustacean features industry news, educational tutorials, crate updates, and current job opportunities in the embedded Rust ecosystem.
An overview of developing a high-performance, DMA-enabled RP2350 I2C driver in Rust that minimizes CPU overhead by offloading transactions from IRQ-heavy patterns.
An overview of the implementation details, modeling techniques, and integration features for the newly added soft-body support in the Rapier physics engine.
Cloudflare introduces experimental support for the `wasm32-unknown-emscripten` target in Workers, enabling native Rust applications—including those using Tokio—to run with improved compatibility.
An analysis of the current Rust SIMD landscape, comparing portable abstractions, compiler-based vectorization, and platform-specific intrinsics as of 2026.
The article explores how to achieve ergonomic API patterns like named, optional, and default arguments in Rust by leveraging existing type-system features instead of adding new language syntax.
This report details ongoing maintenance and infrastructure improvements for the Rust compiler, including work on build directory sizing, Polonius, build system refactoring, and crate management, carried out as part of a Sovereign Tech Fellowship.
This RustConf 2026 talk explores using Rust for real-time software-defined radio, covering the signal processing fundamentals for decoding AM, FM, and ADS-B aircraft data.
A RustConf 2026 talk introduces a prototype aimed at enabling standard Rust code to run directly on GPUs as a first-class compiler target, eliminating the need for specialized ecosystem libraries.
Leveraging type-state patterns by decomposing `std::path::Component` enums into dedicated structs to enforce path manipulation invariants at compile time.
This article provides a comprehensive technical deep dive into how Rust's reborrowing mechanism enables safe, sequential delegation of mutable references through compile-time static analysis.
Propuesta de arquitectura para servicios backend en Rust que organiza el código en torno a reglas de negocio (Domain), operaciones coordinadas (Flows) y dependencias externas (Effects) para evitar la complejidad innecesaria de patrones orientados a objetos.