Mojo Vision Document and Roadmap

Today we released a new document outlining our vision for Mojo to become a programming language to unify development across diverse hardware. It’s a baseline to guide our decision-making as the language evolves, and we’re thrilled to share it.

Mojo plays a key role in Modular’s mission to democratize AI compute. It aims to unify developers across domains, skills, and backgrounds, while unifying hardware with consistent tools and programming models.

With this document, we’re sharing the high-level design principles that guide Mojo’s development. Language design is expensive and difficult, but when done right, it creates value that compounds over time, enabling performance, creativity, composability, and community growth.

We also updated the Mojo Roadmap. With this document, we’re providing a high-level roadmap and directional guidance on how we expect the Mojo programming language to evolve over a series of phases.

Want to learn more? Join us on September 8 at the Modular Community Meeting for a Q&A where the Mojo team will answer all your questions about the vision document and the future of Mojo.

7 Likes

Mojo may or may not evolve into a full superset of Python, and it’s okay if it doesn’t.

We’re encouraged by how well AI-assisted coding tools already help migrate Python to Mojo today, and we’re confident that future tooling and ecosystem maturity will make this evolution even smoother.

So my impression from this is that the Mojo team themselves will not be releasing an official tool to migrate Python code to Mojo; we’ll have to rely on community-made tools for that. Is this correct?

Hi Brian, thanks for posting!

Please do read too much into this sentence. It was meant to say “let’s not look too far into the future yet”. We are too far away from having such a tool, so talking about it would be pure speculation on our part.

1 Like