Chris Lattner

Exactly.

Well, in all seriousness, like, I mean, I think there's really, I'll give you two opposite answers.

One is I hope if it's useful, if it solves problems and people care about those problems being solved, they'll adopt the tech.

That's kind of the simple answer.

And when you're looking to get tech adopted, the question is, is it solving an important problem people need solved?

And is the adoption cost low enough that they're willing to make the switch and cut over and do the pain up front so that they can actually do it, right?

And so hopefully Mojo will be that for a bunch of people.

you know, people building these hybrid packages are suffering.

It's really painful.

And so I think that we have a good shot of helping people.

But the other side is like, it's okay if people don't use Mojo.

Like, it's not my job to say like, everybody should do this.

Like, I'm not saying Python is bad.

Like, I hope Python, CPython, like all these implementations, because Python ecosystem is not just CPython.

It's also a bunch of different implementations with different trade-offs.

And this ecosystem is really powerful and exciting as are other programming languages.

It's not like TypeScript or something is going to go away, right?

And so there's not a winner-take-all thing.

And so I hope that Mojo is exciting and useful to people, but if it's not, that's also fine.

Out of the box before you get to 35,000.