Mojo 1.0 Is Here

Mojo 1.0 Is Here

Modular has officially released Mojo 1.0, marking the language's transition to a stable, production-ready foundation. After years of rapid evolution, Mojo now offers a consistent and predictable development experience, with contributions from nearly 200 community members. This release includes Python-style lambdas, improved LSP stability, and better memory safety diagnostics. Modular also announced plans to open-source the Mojo compiler and toolchain in 2026, and introduced MAX enhancements like support for GLM-5.2 and Nemotron-H models.

Mojo 1.0 does not mark the end of the language’s evolution, but it is an important milestone on a longer journey.
  1. swiftcoder

    I feel like this language would really benefit from some sort of 1-pager overview.

    I just spent a fair bit of time on the official site, and I still don't think I have a very good grasp of what problem this language aims to solve, or why I would select it over other similar languages

  2. redlewel

    Don't see the value of using a language with a closed source compiler...

    Much better options out there. Python already has libraries like Pydantic that offload performance to functions written in Rust under the hood.

  3. oceansky

    AI generated first image does not give me much confidence.

    Lastest OpenCV 5 release notes also had a lot of LLMisms.

    I guess that's the new normal. Still, I am very hopeful for Mojo.

  4. derbOac

    Is Mojo being a superset of Python still part of its projected feature set?

    I tried Mojo a bit early on and decided to come back to it when it was more complete, and in the interim I read some comments somewhere that the superset-of-Python part was being walked back from.

    On https://mojolang.org/docs/roadmap/ it's stated (Phase 3) that "Mojo may or may not evolve into a full superset of Python, and it's okay if it doesn't."

    I feel like that "full superset of Python" part was part of the appeal of Mojo.

    Personally I'm kind of tired of 97% python-compatible this-and-that. Python itself has enough of a history of incompatibility and the cognitive overhead in switching might be easier with just moving to a totally different language. But maybe not — it depends on the details I guess.

    Honestly reading through the documentation more and more I'm more and more confused about what the 1.0 release actually means.

  5. minraws

    > Finally, we will continue to progressively open-source more of the Mojo language, as well as components in MAX that we have built with it. Our commitment remains unchanged – we will open source the Mojo compiler and toolchain in 2026.

    Why not now though? Why wait for 4 more months? What magic is there to hide in just making it source available at least.

  6. alberth

    So is the language itself proprietary licensed, with standard library Apache 2?

    Am I understanding the current state of things correct?

  7. twsted

    Nothing but respect for Chris, and I understand why founders take these deals. But an acquihire usually means the product is the part that gets left behind, and that's the part I cared about.

  8. cuzezzzbbfofai

    Apparently they'll be open sourcing it on August 18th, one week from now.

More from this day

2026-08-11