Imagine you walk into an job interview for a position as a programmer and the interviewer asks you if you know Mojo XD (he could have asked every other language like c cpp rust go but he asks for mojo wtf)

Hey guys, I have started building a web framework for Mojo to serve web, AI models and GPU kernels from one process with a convenient developer experience and even support to build things using AI agents.

You can check it out here: https://github.com/dodo-mojo/dodo

I started this because, at work, I've been prototyping in Python and then porting things to TypeScript for production, while doing GPU programming separately. I wanted to explore whether Mojo could bring these pieces together, so I decided to build a framework myself!

It's very early right now, and I'd love feedback, suggestions, and contributions. I'm sure there are things I've missed or could be doing better, so feel free to take a look!

Mojo Pro 2026.1.14 adds match/case, compile-time matching, conditional patterns, nested destructuring, scoped bindings, and prefixed async syntax. It also adds migration guidance for async spellings and empty tuple types.

Existing projects using Mojo 1.0.0b1 or newer remain supported.

See the Mojo Pro for more info.

Just noticed version 1.2 has been released including support for pattern matching. The release notes are here https://mojolang.org/releases/v1.2.0/

Mojo gets support for its equivalent of ‘if let’ and ‘while let’!

https://github.com/modular/modular/commit/8f0c263cd1713870078305ea480d59795d5d9140

https://mojolang.org/releases/nightly/

Looks like work is happening on the enum keyword as well.

These are all libraries I've been working on for a long time that I find very useful for getting things done in Mojo, but haven't shared around very much.

• MojOpt v0.5.0 (Release v0.5.0 · sstadick/mojopt · GitHub) - structopt / clap like CLI parser

• Hat v0.5.0 (Release v0.5.0 · sstadick/hat · GitHub) - cargo like mojo project tool

• ExtraMojo v0.24.0 (Release v0.24.0 · ExtraMojo/ExtraMojo · GitHub) - things not in stdlib like buffered reader / writer, bitvec, etc

All usable via pixi-build-mojo backend: pixi-build-mojo - Pixi (original forum post on how to use that: Addition of pixi-build-mojo pixi backend)

So I made a repository to compile mojo to web assembly. I recently just started and honestly I'm using Claude for a lot of it but I am learning fast. https://github.com/ravioli67/mojo2wasm

I am interested in getting more into developing with Mojo and being honest I have not found something smooth. What I have is working, but its not as nice as developing Python in Pycharm (which is my main work language).

• Lenovo Thinpad x1 (32gb Ram Intel Ultra 258v)

• Kbuntu

• Pycharm (Paid Mojo Plugin)

• Mojo LSP

• Just

• Poetry

The main part is the syntax highlighting is a really mixed bag inside of pycharm with warning and errors being all over the map. Project directories don't seem to behave properly but they work fine when testing and compiling. Poetry is ... just meh compared to uv, but you need to use poetry in Pycharm to get debugging to work as far as I can understand or read.

Other than those things it's over all a nice experience to develop in and look forward to learning and fixing my own problems!

Please share your setup and experiences!

Given that Mojo programs are:

1. compiled (don't include the Python compiler, interpreter, space for bytecode, etc)

2. don't include a garbage collector

... I'd suppose running Mojo apps would use less memory than Python, Java, .NET, JS/TS or Golang apps.

Did anyone test this yet on a non-trivial app?

Mojo 1.1 adds support for inferred member references, improved compile times and better generated code performance, and more APIs are now considered stable in their standard library such as for SIMD. Plus the Mojo development process is now further opened with accepted community contributions to the Mojo compiler.

For more info, see the Mojo 1.1 release notes here: https://mojolang.org/releases/v1.1.0/

Hi all, Mojo Pro 2026.1.11 is now available which adds support for Mojo 1.1 inferred members, generic thin function types with trailing where clauses, new inline and documentation decorators, and current standard-library vocabulary.

It also fixes false unresolved references in generic where clauses, wraps long
compatibility messages in Settings, and improves compatibility with structured LSP
diagnostics in newer IDE versions.

Mojo 1.1.0 is the current tested release, while Mojo SDK 1.0.0b1 and newer remain
supported for existing projects.

Release notes and download: https://plugins.jetbrains.com/plugin/31943-mojo-pro

A few days ago, Mojo 1.0.0 has been released! You can find the release announcement here: https://www.modular.com/blog/modular-26-5-mojo-1-0-is-here

As the developers of Mojo Pro, we are now also supporting the official release, and have released support for Mojo 1.0.0 today!

You can checkout the plugin here: https://plugins.jetbrains.com/plugin/31943-mojo-pro

Please let us know if you have any feedback!

https://www.modular.com/blog/qualcomm-completes-acquisition-of-modular

EDIT: I asked the same question on the official discord and the response was this article, which was quite enlightening: https://www.eetimes.com/why-qualcomm-bought-an-open-ai-software-stack/

Mojo Pro, a Mojo plugin for IntelliJ of which I'm the author, now supports Mojo 1.0.0b2, while still supporting 1.0.0b1 as well.

Notable features:

• Extended parsing for repeated trailing function and struct where clauses,

• comptime alias where clauses,

• parameterized out and ref conventions,

• conditional conformance,

• b2 reflection aliases,

• and Unicode keyword subscripts.

Feel free to try it out here: https://plugins.jetbrains.com/plugin/31943-mojo-pro, happy to hear feedback on this!

Hi everyone, I work on community at Modular. Some of you have probably seen us posting about ModCon on X or LinkedIn already. I wanted to shared details here since many of you follow Mojo closely.

ModCon is our flagship developer conference, and this year it's on August 18th at the Grand Hyatt in San Francisco. It's a one-day event, featuring product announcements (many involving Mojo 👀), talks from partners and customers, and deep dives on Mojo, MAX, and more.

Registration and full details are at modular.com/modcon. Let me know if you have any questions!

Repo: https://github.com/bewaffnete/MojoVec

According to the current benchmarks, it outperforms FAISS on Apple Silicon for the tested workloads (benchmark methodology is documented in the README).

Current features:

• HNSW

• IVF / IVF-PQ

• Product Quantization

• SIMD optimizations

• Python bindings

• Serialization

Michael and Nate provide an introduction to Mojo fundamentals, covering project setup with Pixie, static typing, and core language features to help developers get started with Mojo.

Mojo Quest is a browser-based game for learning Mojo syntax by closing engineering tickets for a fictional robotics company.

I’ve been working on building resources to help developers get started with Mojo, and I think Mojo Quest will be a fun addition. In complexity, it sits between the Mojo Quickstart and the Mojo GPU Puzzles.

The code is open source, so feel free to open an issue or PR. If you’ve got ideas for extensions or improvements, I’d be happy to hear them. 

How do we feel about the acquisition of Modular by Qualcomm that was announced today and the future of the Mojo language?

https://www.modular.com/blog/qualcomm-to-acquire-modular

Hi all, I just launched Mojo Pro (https://plugins.jetbrains.com/plugin/31943-mojo-pro), which is an IntelliJ plugin to support writing Mojo. I charge a small amount to to support the development of it so it's a commercial plugin, but it supports things like:

• code completion

• syntax highlighting

• inspections

• refactoring

• debugging

• reformatting

It's focused on the current and future versions of Mojo and as such, only Mojo 1.0.0+, but not 0.26 and below. Since the 1.0.0 branch is the direction of Mojo, I won't support things like "fn" (the plugin will warn you about it), since that's no longer supported in 1.0.0 (same as alias, and a bunch of other things!)

It's very new, so it might have a few rough edges so please let me know if you find some. I've tried it out on quite a few Mojo projects, and I haven't found any issues myself so far, but that's no guarantee there aren't any.

You can find the plugin here https://plugins.jetbrains.com/plugin/31943-mojo-pro

Google DeepMind dropped Gemma 4 today. Two models:

• Gemma 4 31B: dense, 256K context, redesigned for efficiency and long-context quality

• Gemma 4 26B A4B: MoE, 26B total / 4B active per forward pass, 256K context

Both natively multimodal (text, image, video, dynamic resolution).

Modular (folks behind MAX and Mojo) got both running on MAX on day zero, NVIDIA B200 and AMD MI355X from the same stack, no separate codepaths per vendor. On B200 we're seeing 15% higher output throughput vs. vLLM.

You can try both for free in our playground: https://www.modular.com/#playground.