Chris Lattner

And you can move C code to C++, and then you can adopt classes.

You can adopt templates.

You can adopt other references or whatever C++ features you want after you move C code to C++.

You can't use templates in C.

Right?

And so if you leave it to C, fine, you can't use the cool features, but it still works, right?

And C and C++ code work together.

And so that's the analogy, right?

Now, here, right, there's not a Python is bad and a Mojo is good.

Mojo just gives you superpowers.

And so if you want to stay with Python, that's cool.

But the tooling should be actually very beautiful and simple because we're doing the hard work of defining a superset.

Exactly.

Once you're in the new world, then you can build all kinds of cool tools to say, hey, should you adopt this feature?

And we haven't built those tools yet, but I fully expect those tools will exist, and then you can quote-unquote modernize your code or however you want to look at it.

So one of the things that I think is really interesting about Mojo is that

There have been a lot of projects to improve Python over the years.

Everything from getting Python run on the Java virtual machine, PyPy, which is a JIT compiler.

There's tons of these projects out there that have been working on improving Python in various ways.

they fall into one of two camps.