Chris Lattner

But when you're working with people, and you're working with code and dusty deck code bases and things like this, it's not about what's theoretically beautiful.

It's about what's practical, what's real, what people actually use.

And I don't meet a lot of people that say, I want to rewrite all my code.

Just for the sake of it.

I have talked with him about it.

He found it very interesting.

We actually talked with Guido before it launched, and so he was aware of it before it went public.

I have a ton of respect for Guido for a bunch of different reasons.

You talk about Walrus Operator, and Guido is pretty amazing in terms of

steering such a huge and diverse community and and and like driving it forward and i think python is what it is thanks to him right and so to me it was really important starting to work on mojo to get his feedback and get his input and get his eyes on this right now um a lot of what guido was is was and is i think concerned about is how

How do we not fragment the community?

We don't want a Python 2 to Python 3 thing.

That was really painful for everybody involved.

And so we spent quite a bit of time talking about that and some of the tricks I learned from Swift, for example.

So in the migration from Swift, we managed to not just convert Objective-C into a slightly prettier Objective-C, which we did.

We then converted, not entirely, but

almost an entire community to a completely different language, right?

And so there's a bunch of tricks that you learn along the way that are directly relevant to what we do.

And so this is where, for example, you leverage CPython while bringing up the new thing.

That approach is, I think, proven and comes from experience.