Adam Leventhal

I mean, I feel we said this when we, again, ringing the chime for unknown episode, but I feel we said this when we first started talking about LLMs and Rust, that like actually Rust is going to be a really good fit for these things because you get the, I mean, Rust, something I've said from the beginning, that Rust shifts the cognitive load to the developer in development.

And it forces the developer in development to consider a lot of issues that historically you wouldn't see until some code is deployed into production.

And I loved that shift.

I think that shift is really important.

I think that, like, that tacks right into what LLMs can do.

And I think that it's, that they reinforce one another.

So I think, like, LLMs, I think, and Rust are a very good fit for one another.

Which I don't think is that hot to take.

I don't think that's that spicy.

Okay.

Easy, easy, easy, easy.

Listen, we're not living in that kind of a future yet, pal.

No, I think the ASI is going to be like, I actually don't know what this is.

I can't make sense of this thing.

It's like, it's a 2K long.

Yeah, that is really interesting.

When I just think just in general, having the great type information, I mean, the code that I would be scared, that to me would scare me the most would be just like pure JavaScript.

I know it generates a lot of it, but we use TypeScript.

I mean, David, correct me if I'm wrong, we use TypeScript for more or less anything, everything.

It would really terrify me to use because it's just so easy to have an issue that doesn't show up until you get into runtime.