LOADING
In this talk, we'll dive deep into what makes concurrency coordination costly, and explore some pathways to mitigate that cost.
Modern hardware is moving to more cores rather than faster ones. For application developers, this means that further performance gains require _parallelism_; making progress on many tasks at the same time. But as anyone with experience writing multi-threaded code will tell you, this is easier said than done — those threads inevitably have to coordinate, and coordination is "expensive."
But _why_ is it expensive? Sure, a mutual exclusion lock forces sequential execution, which limits overall speedup (per Amdahl's law). But is the lock itself expensive? Do reader-writer locks help when the coordination is mostly required for reads? In this talk, we'll dive deep into what makes concurrency coordination costly, and explore some pathways to mitigate that cost. By the end, you'll leave with a mental model that goes all the way down to the CPU cache line, and a newfound appreciation for a protocol from the 1980s.
We’ll take a deep dive into Rust channels — from synchronous channels to asynchronous channels — to explore how message passing enables reliable concurrent programming.
In this introductory talk, we will explore what it means to "Ratatuify" the Rust package manager, Cargo.
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them.
As Rust projects grow, managing private crates becomes a real headache. Teams struggle with inconsistent versioning, fragile dependencies, and cumbersome workflows that slow down development. In this talk, I’ll walk through how these challenges can be solved with Rust and CrabHub.
