Chris Lattner

Yes.

And then, or you want to build on top of a bunch of other people's packages and then they get updated and things like this.

Now, I'm not an expert in this, so I don't know the answer.

I think this is one of the reasons why it's great that we work as a team and there's other really good and smart people involved.

But one of the things I've heard from smart people who've done a lot of this is that the packaging becomes a huge disaster when you get the Python and C together.

And so if you have this problem where you have code split between Python and C, now not only do you have to package the C code, you have to build the C code.

C doesn't have a package manager, right?

C doesn't have a dependency versioning management system, right?

And so I'm not experienced in the state of the art and all the different Python package managers, but my understanding is that's a massive part of the problem.

And I think Mojo solves that part of the problem directly heads on.

Now, one of the things I think we'll do with the community, and this isn't, again, we're not solving all the world's problems at once.

We have to be kind of focused to start with, is that I think that we will have an opportunity to reevaluate packaging, right?

And so I think that we can come back and say, okay, well, given the new tools and technologies and the cool things we have that we've built up, because we have not just syntax, we have an entirely new compiler stack that works in a new way.

Maybe there's other innovations we can bring together and maybe we can help solve that problem.

Well, I mean, it's kind of funny because this is one of the challenges of these intentionally decentralized communities.

And so I don't know what the right answer is for Python.

I mean, there are many people that would

I don't even know the right answer for Mojo.

So there are many people that would have much more informed opinions than I do.

But it's interesting if you look at this, right?