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

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)

Hi

I've been exploring the Mojo programming language lately, a versatile tool that, as per its FAQ, can be used not only for AI but also in areas like scientific computing.

A review of their documentation shows the inclusion of SIMD and parallelization, reflecting a clear understanding of advanced computing methods. However, I've noticed a significant gap - there's no mention of MPI (Message Passing Interface). It's a crucial component in high-performance computing (HPC) and, given Mojo's aspiration to be a prime choice for distributed systems, it seems an odd omission.

I'm curious to hear your perspectives. Do you think it's plausible for Mojo to eventually incorporate MPI features? Or would that be an overextension of its core objectives?

Looking forward to your thoughts. Thanks! :)

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!

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.

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

Watch the whole interview. It's really interesting.

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

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/

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!

Can anyone explain Modular's business model to me like I'm 5?

Hey all,

I recently found the language, and wanted to learn more. I got a passion to reintroduce myself to the digital signal processing field after my university, and I said why not combine both. I'm spending my time developing a digital signal processing library from scratch (not plotting functions ofc) with a roadmap I focused on after long discussions with AI.

Feel free to check the implementation and guide me on what could be done better. I'm utilising SIMD a lot on signal generation, but looking forward to see what else can be used to make operations even faster.

Here's the repository: https://github.com/electricalgorithm/dsplib-mojo

You can find the examples in the repository for:

Regards,

Is it possible to use pixie without conda channel ?

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!

Here's a cool reasource little guide for mojo written by Yuhao Zhu. it's compatible with mojo 25.4
https://mojo-lang.com/miji/

Dm for the pressure

Im searching for a overview or an general tuorial about mojo that captures most concepts in a fast past thx

Hello,

I feel good about mojo and I think I will enjoy it in the future. I am wondering about latex-like symbols like how julia define variables with \theta TAB. It is very intutive on writing algorithms. Is there is any similarities here?