Chris Lattner

Python has a feature called async await.

So it's a new feature.

I mean, in the long arc of Python history, it's a relatively new feature, right?

That allows way more expressive asynchronous programming.

Okay.

Again, this is a, Python's a beautiful thing and they did things that are great for Mojo for completely different reasons.

The reason the async await got added to Python, as far as I know, is because Python doesn't support threads.

And so Python doesn't support threads, but you want to work with networking and other things like that that can block.

I mean, Python does support threads.

It's just not its strength.

And so they added this feature called async await.

It's also seen in other languages like Swift and JavaScript and many other places as well.

Async await in Mojo is amazing because we have a high performance heterogeneous compute runtime underneath the covers that then allows non-blocking IO so you get full use of your accelerator.

That's huge.

It turns out it's actually really an important part of fully utilizing the machine.

You talk about design discussions.

That took a lot of discussions, right?

And it probably will require more iteration.

And so my philosophy with Mojo is that, you know, we have a small team of really good people that are pushing forward and they're very good at

the extremely deep knowing how the compiler and runtime and all the low-level stuff works together, but they're not perfect.