Matthias Endler

It's Rostium Production, a podcast about companies who use Rost to shape the future of infrastructure. I'm your host, Matthias Endler from Corot, and today we talk to Julius Gustafsson from Volvo about putting the good kind of Rost into cars. Julius, thanks for being a guest. Thanks for taking the time. Can you introduce yourself and Volvo, the company you work for?

It's Rostium Production, a podcast about companies who use Rost to shape the future of infrastructure. I'm your host, Matthias Endler from Corot, and today we talk to Julius Gustafsson from Volvo about putting the good kind of Rost into cars. Julius, thanks for being a guest. Thanks for taking the time. Can you introduce yourself and Volvo, the company you work for?

It's Rostium Production, a podcast about companies who use Rost to shape the future of infrastructure. I'm your host, Matthias Endler from Corot, and today we talk to Julius Gustafsson from Volvo about putting the good kind of Rost into cars. Julius, thanks for being a guest. Thanks for taking the time. Can you introduce yourself and Volvo, the company you work for?

The first time I heard about this project was even a few years ago when we were at a conference. I can't even remember which one. But someone mentioned that Volvo was working with Rust. And by Rust, we mean Rust, the programming language, of course, not Rust, the oxidation process.

The first time I heard about this project was even a few years ago when we were at a conference. I can't even remember which one. But someone mentioned that Volvo was working with Rust. And by Rust, we mean Rust, the programming language, of course, not Rust, the oxidation process.

The first time I heard about this project was even a few years ago when we were at a conference. I can't even remember which one. But someone mentioned that Volvo was working with Rust. And by Rust, we mean Rust, the programming language, of course, not Rust, the oxidation process.

But it was way back in the day, and I didn't even know what parts of it were public or if that was a separate vendor. Now, take us back to maybe 2018 or so when this project started. What was the situation with Rust back then? What was the situation, especially with embedded Rust? And how did you even think about using Rust at Volvo?

But it was way back in the day, and I didn't even know what parts of it were public or if that was a separate vendor. Now, take us back to maybe 2018 or so when this project started. What was the situation with Rust back then? What was the situation, especially with embedded Rust? And how did you even think about using Rust at Volvo?

But it was way back in the day, and I didn't even know what parts of it were public or if that was a separate vendor. Now, take us back to maybe 2018 or so when this project started. What was the situation with Rust back then? What was the situation, especially with embedded Rust? And how did you even think about using Rust at Volvo?

How much of that was because of Rust and how much of it was because of your experience with embedded systems?

How much of that was because of Rust and how much of it was because of your experience with embedded systems?

How much of that was because of Rust and how much of it was because of your experience with embedded systems?

Why did you decide to build that with AsyncRust, given that it was still in an alpha version? Couldn't you have done something with Syncrust?

Why did you decide to build that with AsyncRust, given that it was still in an alpha version? Couldn't you have done something with Syncrust?

Why did you decide to build that with AsyncRust, given that it was still in an alpha version? Couldn't you have done something with Syncrust?

A lot of backend developers hearing that might be a bit scared by the way AsyncRust worked back in the day where even back in the day, I think you needed to build your own futures. Was that still the case back then?

A lot of backend developers hearing that might be a bit scared by the way AsyncRust worked back in the day where even back in the day, I think you needed to build your own futures. Was that still the case back then?

A lot of backend developers hearing that might be a bit scared by the way AsyncRust worked back in the day where even back in the day, I think you needed to build your own futures. Was that still the case back then?

And you still saw the potential there, even though it was a bit, let's say, half-baked or it wasn't completely fleshed out yet?

And you still saw the potential there, even though it was a bit, let's say, half-baked or it wasn't completely fleshed out yet?