Upcoming changes to our GitHub repositories

Modular Official Announcements
1

Tomorrow (February 27), we’re streamlining our GitHub repositories! The max repo is merging into the mojo repo, bringing everything under one roof. A new subdirectory will house the Mojo standard library and examples. Once the merge is complete, the max repo will be deleted, and the mojo repo will be renamed to max.

What does this mean for you?

  • If you’re working with the Mojo or MAX repos locally, you’ll need to update your remote repository’s URL(s) to reference the updated repo URL. Here are instructions for making this change.
  • Although the MAX examples and Mojo standard library will be located in the same repository, we won’t be accepting contributions to MAX examples.
  • All open PRs on the Mojo repo will be rebased after the transition.
  • All open MAX Issues will be reviewed and migrated after the transition.

Got questions? Let us know—we’re here to help!

2

Does this indicate any sort of internal shift away from viewing or prioritizing Mojo as its own standalone, general purpose, language?

3

Hi @duck_tape,

Mojo is a fundamental technology that enables us to build the MAX platform. Our long-term vision is for Mojo to be the best programming language for portable high-performance computation, and unifying the repositories enables us to work faster in delivering MAX as the best platform for putting AI workloads into production.

1 Like
4

To +1 Caroline, we’ve always maintained that Mojo🔥 is useful for a wide variety of purposes, but a major differentiator for is in GPU and xPU programming. To enable those use-cases we want to provide the runtime and other required capabilities in an easy to use way.

That doesn’t prevent using subsets of the tech: you don’t need a GPU runtime on CPU :-), but if you’re on GPU then we want everything to be simple and easy and “just work”. These goals aren’t in tension given our “Modular” approach to layering and lack of dependencies.

-Chris

2 Likes
5

I appreciate the reply!

Even with the announcement noting that this was an ergonomic change, it did feel like a step back for Mojo the language to no longer have its own repo. As such, it’s meaningful to see the original assurances and motivations around Mojo restated.

Continually impressed by the communication around the project as it balances the internal development with external tinkering.

1 Like