--- title: Modular: Modular 26.5: Mojo 1.0 is here! | daily.dev description: Mojo programming language has officially reached version 1.0, marking a stable, production-ready milestone after its initial release in 2023. The 1.0 release... canonical: https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Modular: Modular 26.5: Mojo 1.0 is here! | daily.dev og:description: Mojo programming language has officially reached version 1.0, marking a stable, production-ready milestone after its initial release in 2023. The 1.0 release... og:url: https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq og:image: https://api.daily.dev/og/posts/Pko4OvBVQ.png og:image:alt: Modular: Modular 26.5: Mojo 1.0 is here! og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Modular: Modular 26.5: Mojo 1.0 is here! **[Hacker News](https://daily.dev/sources/hn)** · 5 min read · 12 upvotes · 1 comments ## Summary Mojo programming language has officially reached version 1.0, marking a stable, production-ready milestone after its initial release in 2023. The 1.0 release prioritizes language stability, with changes during the 1.x timeframe expected to be primarily additive. Key improvements include Python-style lambda syntax for inline closures, a more stable LSP server, memory safety diagnostics for reference invalidation, and unified language constructs (single Pointer type, consistent var declarations). Nearly 200 community contributors landed over 1,100 pull requests changing 200,000+ lines of code. The MAX platform also gains easier installation via extras syntax, support for GLM-5.2 and Nemotron-H hybrid Mamba-2 model families, and Kimi 2.5 compatibility with Module V3. Future plans include async programming, pattern matching, unions, and open-sourcing the Mojo compiler and toolchain in 2026. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What changed in Mojo 1.0 compared to earlier beta versions? Mojo 1.0 finalizes a round of language simplification: variables are now consistently declared with var, closures have been unified into one form, there is a single Pointer type, and several APIs were renamed for consistency. It also adds Python-style lambda syntax, a more stable LSP server, and diagnostics for reference invalidation such as List.append breaking existing references. _Track Mojo 1.0 language changes and migration details as they land by following updates on daily.dev._ ### Will Mojo 1.0 introduce breaking changes in future releases? Yes, but they will be managed carefully rather than happening frequently. During the 1.x timeframe, changes are meant to be primarily additive so existing code keeps working, following the approach mature languages like C++ use when evolving over time, giving developers confidence to build long-term projects on Mojo. _Developers planning long-term Mojo projects can follow versioning changes closely via daily.dev._ ### When will the Mojo compiler and toolchain be open sourced? The Mojo compiler and toolchain are planned to be open sourced in 2026, continuing a progressive open-sourcing effort that already includes the standard library, which has received over 1,100 pull requests from nearly 200 contributors changing more than 200,000 lines of code. _Anyone evaluating Mojo's open source roadmap can keep tabs on the timeline through daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 119 comments across lobsters, hackernews (as of 2026-09-14). **TL;DR:** The community acknowledges Mojo 1.0 as a technically interesting milestone but is broadly skeptical, with the closed-source compiler being the dominant concern; many say they won't adopt it until the compiler is open-sourced, which is expected around August 18. **Sentiment:** 20% positive · 40% mixed · 40% skeptical **The case for** - Mojo's use of MLIR enables more sophisticated compiler transformations and direct GPU targeting beyond a typical LLVM wrapper. - The ownership/borrow-checker model, comptime features, and first-class SIMD support make it genuinely compelling for systems and GPU programming. - LLMs lower the barrier to learning a new language, making Mojo's Python-like syntax an easier on-ramp than ever. - Nearly 200 community contributors and 1,100+ PRs signal real momentum around the project. **The pushback** - The compiler remains closed source at 1.0, which many developers consider a dealbreaker for adoption and trust. - The original 'full superset of Python' promise has been quietly walked back, undermining a key part of the initial pitch. - No performance benchmarks comparing Mojo to PyTorch, Triton, or ThunderKittens were provided alongside the 1.0 release. - The Qualcomm acquisition raises concerns that the product (language/ecosystem) may be deprioritized in favor of the team. - The website and marketing materials are confusing about what problem Mojo solves and how it differs from alternatives like Triton or Nim. - AI-generated imagery in the release blog post struck many as cheap and undermining confidence in the project's seriousness. **By community** - lobsters (mixed): No comments were posted, so no community signal is available. - hackernews (skeptical): Broadly skeptical: the closed-source compiler dominates criticism, the Python-superset pivot disappointed many, and while technical merits (MLIR, ownership model) are acknowledged, most say they'll wait for open-sourcing before seriously evaluating Mojo. **Hottest debate:** Whether releasing 1.0 with a still-closed-source compiler is acceptable or fundamentally undermines trust in the project. **Open questions** - When exactly will the compiler be open-sourced, and will it happen at the August 18 Modcon event as widely speculated? - Is Mojo still targeting full Python superset compatibility, or has that goal been officially abandoned? - How does Mojo's real-world performance compare to PyTorch+Triton or ThunderKittens on actual GPU workloads? - What does the Qualcomm acquisition mean for Mojo's long-term roadmap and independence? - How well do current LLMs generate Mojo code given its divergence from Python? **Highlights** > Having written a lot of Mojo over the last two year, just for fun, it's a really cool language. Ownership model adjacent to Rust, comptime in the realm of Zig, rich type system, first class SIMD support, etc. Performance wise it's the first language in long time that isn't just an LLVM wrapper. LLVM is still involved, but they are using it differently than say, Rust or Zig. Very excited for Mojo once it's open sourced later this year. > — [totalperspectiv on hackernews · 3 comments](https://news.ycombinator.com/item?id=49263579) > Ladybird is Open Source and doesn't accept outside contributions any more same with sqlite and many other projects. Lots of Google's oss projects also are not very open to contribution. At this point I find it deeply troubling that it isn't open source. I respect Chris I know folks who have worked with him and but at the end of the day I feel too weird about this entire closed source programming language thing. If we complain to Nvidia about there weird closed source limitations, I think Mojo is just as bad. You don't even know what your compiler might be doing, and if it does something wrong you can't fix it, you now have to file a bug and wait until the gods from above come to your rescue. I have had similar issues with drivers, I have faced soo many driver bugs in my work and the answer is always write more code that works around it somehow, this warp level is bad, this feature doesn't work with these values, etc. etc. Why can't I fix them, I have often on Linux just pinged the Mesa team about driver bugs with a rough draft of a patch and gotten it fixed, I can even patch and run it myself when I am in a hurry. I feel like atleast making stuff, source available like Unreal should be the baseline for any "core" software where a bug could possibly be a major blocking issue for a developer. Windows and Mac are very bad with this. Mac's CoreML has had soo many bugs over the last couple years I have had to email someone I know at the company to get them fixed or try to get into contact with someone. Intel's drivers have had bugs too but I have had more contacts there which is a wash. AMD well it's AMD... Either way closed software sucks I don't want to use fully closed stuff unless I don't have a choice people can make what they want of it. I don't really care. I care much less about just foss. > — [minraws on hackernews](https://news.ycombinator.com/item?id=49264321) > 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. > — [derbOac on hackernews · 2 comments](https://news.ycombinator.com/item?id=49264143) > The value has already been materialized. They were acquired by Qualcomm for $3.9 billion. > — [woadwarrior01 on hackernews · 3 comments](https://news.ycombinator.com/item?id=49263388) > And Mojo will die because nvidia is not interested in maintaining any semblance of backwards compatibility when it comes to CUDA. It's going to be a perpetual race forwards, and whenever nvidia upgrades CUDA, you're going to be stuck there twiddling your thumbs and waiting for Mojo to become compatible. Additionally, anyone who has seen how Swift evolved should be wary of Lattner saying "the language is mostly stable", or even "the language is released". > — [well\_ackshually on hackernews · 1 comments](https://news.ycombinator.com/item?id=49263360) **Source threads** - [lobsters](https://lobste.rs/s/r8qb5p/mojo_1_0_is_here) · 1 points · 0 comments - [hackernews](https://news.ycombinator.com/item?id=49261128) · 248 points · 119 comments ## Community discussion Top comments from developers on daily.dev. **@tripi\_wick** · 1 upvotes > Finally, Mojo is getting into shape. Really excited to see what it does in future because it's a super set of Python and we all know that which languagebis currently in global usage 🔥✌️ ## Similar posts on daily.dev - [Mojo 1.1 Released, Now Accepting Community Contributions To The Compiler](https://daily.dev/posts/mojo-1-1-released-now-accepting-community-contributions-to-the-compiler-ajle2rdfp) · Phoronix · 0 upvotes · 0 comments - [Revisiting Mojo: A faster Python?](https://daily.dev/posts/revisiting-mojo-a-faster-python--f2vgwvnmd) · InfoWorld · 6 upvotes · 0 comments - [Mojo's not \(yet\) Python](https://daily.dev/posts/mojo-s-not-yet-python-xpvwa4uas) · Lobsters · 1 upvotes · 0 comments --- Tags: [#gpu](https://daily.dev/tags/gpu) [View this post on daily.dev](https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Modular: Modular 26.5: Mojo 1.0 is here!","url":"https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq"},"datePublished":"2026-08-11T19:01:55.348Z","dateModified":"2026-09-14T08:06:01.289Z","description":"Mojo programming language has officially reached version 1.0, marking a stable, production-ready milestone after its initial release in 2023. The 1.0 release...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/45c6589cb09e9856963e5015a518ee06?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/45c6589cb09e9856963e5015a518ee06?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":12},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"gpu","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Modular: Modular 26.5: Mojo 1.0 is here!"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq","comment":[{"@type":"Comment","text":"Finally, Mojo is getting into shape. Really excited to see what it does in future because it’s a super set of Python and we all know that which languagebis currently in global usage 🔥✌️","datePublished":"2026-08-11T21:23:52.037Z","url":"https://daily.dev/posts/Pko4OvBVQ#c-ox7EFsv4U","author":{"@type":"Person","name":"Trishan Preet Singh","url":"https://daily.dev/tripi_wick","image":"https://lh3.googleusercontent.com/a/ACg8ocKD2Q28GJQC962XJvU16Y0CFwBdef4-H9P65XOZIm6oYtwL9p8=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/modular-modular-26-5-mojo-1-0-is-here--pko4ovbvq#faq","mainEntity":[{"@type":"Question","name":"What changed in Mojo 1.0 compared to earlier beta versions?","acceptedAnswer":{"@type":"Answer","text":"Mojo 1.0 finalizes a round of language simplification: variables are now consistently declared with var, closures have been unified into one form, there is a single Pointer type, and several APIs were renamed for consistency. It also adds Python-style lambda syntax, a more stable LSP server, and diagnostics for reference invalidation such as List.append breaking existing references. Track Mojo 1.0 language changes and migration details as they land by following updates on daily.dev."}},{"@type":"Question","name":"Will Mojo 1.0 introduce breaking changes in future releases?","acceptedAnswer":{"@type":"Answer","text":"Yes, but they will be managed carefully rather than happening frequently. During the 1.x timeframe, changes are meant to be primarily additive so existing code keeps working, following the approach mature languages like C++ use when evolving over time, giving developers confidence to build long-term projects on Mojo. Developers planning long-term Mojo projects can follow versioning changes closely via daily.dev."}},{"@type":"Question","name":"When will the Mojo compiler and toolchain be open sourced?","acceptedAnswer":{"@type":"Answer","text":"The Mojo compiler and toolchain are planned to be open sourced in 2026, continuing a progressive open-sourcing effort that already includes the standard library, which has received over 1,100 pull requests from nearly 200 contributors changing more than 200,000 lines of code. Anyone evaluating Mojo's open source roadmap can keep tabs on the timeline through daily.dev."}}]} ```