SPEAKER 1:

Apologize to the simultaneous translators because I have no idea how you would translate this into Japanese.

Um, so one of the things we've talked a lot about over the last few kernel releases is the introduction of rust into the kernel, and I think it has been relatively steady and quiet.

What's your perception?

SPEAKER 2:

Well, so rust still is at the point where we don't.

We have the initial infrastructure got merged last year.

Um, it's been growing, but we don't have any part of the kernel that really depends on rust yet to me.

Rust was.

One of those things that aid made technical sense.

But to me personally, even more important was that we need to not stagnate as as a kernel and as developers.

And so I am always excited by trying something new and not getting too comfortable doing the same thing.

I mean, I've been working on on the kernel now for 32 years.

Yeah, 32 years.

And that's a long time to work on one single thing.

But it's still interesting because it's not the same single thing.

I mean, Linux 32 years ago was very different from what Linux is today, obviously.

And I actually often look for things where where we can do new things and we can do things differently because it's so easy to get stuck in a rut and say, this is working just fine, right?

And and rust has not really shown itself as the next great big thing.

But I think during next year we'll actually be starting to integrate.

Drivers and some even major subsystems that are starting to actively use it.

So it's one of those things.

It's going to take years before it's a big part of the kernel, but it's it's certainly shaping up to be one of those.

SPEAKER 1:

So you're writing rust code yourself.

You're reviewing rust.

SPEAKER 2:

Code.

Oh no, no, I have been reading rust code a bit, just so that I can make some kind of judgment calls on on when something is too horrendous to be included in the kernel.

But I have to admit, no, I, um, I mean, the kernel, we rely on literally thousands of people every single release.

We have a thousand people involved, and they're not the same thousand people.

Quite often we have people.

In fact, for the longest time we've had the statistics be roughly that every release, about half the people involved send just one patch.

And a lot of them never show up again.

They may have something small they wanted to fix that they cared about, and they were not really kernel people.

They found it for some other reason, and they sent their small patch to the kernel, and they were never interested in doing anything more.

But then.

The other half keeps coming back.

And.

And when it comes to rust, I'm not going to be the one who manages the rust, because that's not my expertise, as is true of so many other parts of the kernel.

I'm honestly, I'm less of a programmer these days than I am.

I call myself a technical lead because I'm not a manager.

I don't manage people, I manage code, so I call myself a technical lead.

I'm not.

I'm not.

My day to day work is not programming.

It is merging other people's codes.

And rust will be one of those things.