Apr 2026
13 Mon
14 Tue
15 Wed
16 Thu
17 Fri
18 Sat 09:00 AM – 06:00 PM IST
19 Sun 09:00 AM – 06:00 PM IST
Ravi Sawlani
@gravityvi
Submitted Mar 8, 2026
One language, front to back — with memory safety and no regrets.
The web has converged on one language — and for good reason. A unified stack means less context switching, shared tooling, and faster teams. But that language has a ceiling: no compile-time memory safety, no guaranteed freedom from data races, and performance that tops out well before Rust’s floor.
Rust offers the same promise — one language, front to back — but with things the current dominant stack simply cannot give you. With Leptos in the browser via WebAssembly and Axum on the server, you get a unified stack that is also fast, memory-safe, and verified by the compiler before it ever ships.
This isn’t a thought experiment. I’ve been running a full-stack Rust application in production for over two years. This talk is the honest account of what that looks like — the bugs the compiler caught before they shipped, the performance numbers, the rough edges, and why I wouldn’t go back.
Introduction (2 mins)
The web’s ceiling — why the dominant stack isn’t enough (5 mins)
Rust for the whole stack: Leptos + Axum (5 mins)
What the compiler saves you from (5 mins)
Examples from production (8 mins)
Live demo (5 mins)
Web developers, backend engineers, and anyone evaluating Rust for their next project.
Ravi Sawlani is Lead Rust Developer at Yral, where he leads all Rust engineering and has spent the last two and a half years building and running Rust services in production on self-hosted infrastructure. Before Yral, he worked in the Open Source Program Office at Browserstack maintaining Nightwatchjs — a role he continues to hold today.
He has spoken at several conferences and meetups:
Hosted by
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}