Gergely Orosz

Rust is quietly spreading as a language of choice to build reliable and performant applications.

But what makes it different?

Alice Riel is a software engineer working on Google's Android Rust team, a core maintainer of Tokio, the de facto async runtime for Rust, and is a Rust language team advisor.

In today's conversation, we cover the pitch on why Rust is worth to consider whether you are using TypeScript or C++ today.

how concepts like ownership, the borrow checker, and the unsafe keyword work, and what are things that trip up newcomers to Rust, how the languages govern without a benevolent dictator, and how RFCs and additions work, and many more.

If you want to understand what makes Rust different and why so many engineers say, once it compiles, it works, this episode is for you.

This episode is presented by Intesys.

Verify your system's correctness without human review or traditional integration tests and avoid bugs or outages.

This episode is brought to you by Sentry.

Sentry is application monitoring software built by developers for developers.

The first time I used Sentry was 10 years ago, back at Uber, where Sentry helped keep us honest on when and where our services were breaking.

I also use Sentry today to help me understand if the services and APIs I built for the pragmatic engineer are healthy or not.

Sentry shows you the full context on issues, stack traces, user actions, environment details, and even the exact line of code that caused the issue.

It supports pretty much every modern tech stack, TypeScript, JavaScript, Python, Go, and others.

It works on backend, frontend, mobile, you name it.

One new feature Sentry launched is Seer, their AI debugging agent.

Let me show you.

I open the Seer agent and ask about what are some repeated errors happening on my backend.

Seer figures out that a repeated issue is a network call failure.

I can then ask for more details and debug more efficiently with this AI agent integrated neatly into Sentry.