LOADING
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them.
The Rust web ecosystem has made incredible progress, but let's talk about what we don't discuss enough: the rough edges. Every web developer working in Rust has battled macro-heavy frameworks that obscure what's actually happening, ORM integration headaches that turn simple queries into type gymnastics, and error handling that makes it hard to return clean, user-friendly error messages instead of exposing internal implementation details.
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them. We'll discuss common developer frustrations, emerging patterns and solutions, and honest assessments of what's improving versus what remains challenging. Whether you're shipping production Rust backends or evaluating the ecosystem, you'll walk away with a clearer picture of the real-world challenges and where the community is headed.
This session we will delve into the sometimes murky world of procedural macros - showing some of the great tooling available for understanding the code generated, such as cargo expand, and the key building blocks we will need for writing our own.
We’ll take a deep dive into Rust channels — from synchronous channels to asynchronous channels — to explore how message passing enables reliable concurrent programming.
I'll initiate you in the art of 'CAN bus sniffing': Connecting to the central nervous system of a modern car, interpreting the data, and seeing what we can build as enthousiastic amateurs.
This talk explains how Rust debugging actually works: how compiler-generated debuginfo (DWARF/PDB) maps binaries back to source, and how LLDB/GDB interpret that data in practice.
