Mojo 1.0 Beta

#1

Post by sbt567 » Fri, May 08, 2026, 2:49 AM UTC

Re: Mojo 1.0 Beta

#2

Post by pjmlp » Fri, May 08, 2026, 5:33 AM UTC

Still phase one, doesn't do native Windows.

Meanwhile Julia is more mature for the same purposes, and since last year NVidia is having feature parity between Python and C++ tooling on CUDA.

Python cuTile JIT compiler allows writing CUDA kernels in straight Python.

AMD and Intel are following up with similar approaches.

So will Mojo still arrive on time to gain wider adoption?

Time will tell.

Re: Mojo 1.0 Beta

#3

Post by dllu » Fri, May 08, 2026, 5:49 AM UTC

I remember reading about this 4 years ago as the new Chris Lattner project and was super excited, though a little skeptical.

I think that nowadays with vibe/agentic coding, high performance Python-like languages become ever more important. Directly using AI agents to code, say, C++, is painful as the verbose nature of the language often causes the context window to explode.

Re: Mojo 1.0 Beta

#4

Post by modeless » Fri, May 08, 2026, 5:57 AM UTC

When I first heard about Mojo I somehow got the impression that they intended to make it compatible with existing Python code. But it seems like they are very far away from that for the foreseeable future. I guess you can call back and forth between Python and Mojo but Mojo itself can't run existing Python code.

Re: Mojo 1.0 Beta

#5

Post by 0xpgm » Fri, May 08, 2026, 6:02 AM UTC

Right now majority of beginners start programming with a high-level language, say Python or JavaScript - then for more advanced system-level tasks pickup C/C++/Rust/Zig etc.

If Mojo succeeds, it could be the one language spanning across those levels, while simplifying heterogeneous hardware programming.

Re: Mojo 1.0 Beta

#6

Post by haskman » Fri, May 08, 2026, 6:05 AM UTC

modeless wrote: post #4

When I first heard about Mojo I somehow got the impression that they intended to make it compatible with existing Python code. But it seems like they are very far away from that for the foreseeable future. I guess you can call back and forth between Python and Mojo but Mojo itself can't run existing Python code.

Really the only thing good about Python is its ecosystem.

Re: Mojo 1.0 Beta

#7

Post by boxed » Fri, May 08, 2026, 6:07 AM UTC

dllu wrote: post #3

I remember reading about this 4 years ago as the new Chris Lattner project and was super excited, though a little skeptical. I think that nowadays with vibe/agentic coding, high performance Python-like languages become ever more important. Directly using AI agents to code, say, C++, is painful as the verbose nature of the language often causes the context window to explode.

Not to mention that C++ basically can't be made to be safe. But Rust is probably fine.

Re: Mojo 1.0 Beta

#8

Post by logicchains » Fri, May 08, 2026, 6:08 AM UTC

Very bold of them expecting people to use a language with a closed source compiler in the 2020s.

Re: Mojo 1.0 Beta

#9

Post by insumanth » Fri, May 08, 2026, 6:08 AM UTC

I was excited when Mojo launched and thought it might grow big quick. I don't see much traction. The pitch is compelling. What could be the issue?

Re: Mojo 1.0 Beta

#10

Post by ainch » Fri, May 08, 2026, 6:09 AM UTC

As someone in ML who's interested in performance, I'm keen for Mojo to succeed - especially the prospect of mixing GPU and CPU code in the same language. But I do wonder if the changes they're making will dissuade Python devs. The last time I booted it up, I tried to do some basic string manipulation just to test stuff out, but spent an hour puzzling out why `var x = 'hello'; print(x[3])` didn't work, and neither did `len(x)` (turns out they'd opted for more specific byte-vs-codepoint representations, but the docs contradicted the actual implementation).

Hopefully they get Mojo to a good place for more general ML, but at the moment it still feels quite limited - they've actually deprecated some of the nice builtins they had for Tensors etc... For now I'll stick with JAX and check in periodically, fingers crossed.