News for hackers. Stuff that matters.
Re:Mojo 1.0 Beta by ainch on Friday May 08, 2026 @02:09AM (#48059237)
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.

Re:Mojo 1.0 Beta by coldtea on Friday May 08, 2026 @03:46AM (#48059961)
>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.

Unless it's open sourced, it's a moot point, as most Python devs wont come anyway.

Re:Mojo 1.0 Beta by Certhas on Friday May 08, 2026 @03:57AM (#48060060)
This is a bit ironic, given that people seem to have no problem using CUDA all over the place... Plus they promise to open source with the 1.0 release. We'll see...
Re:Mojo 1.0 Beta by _aavaa_ on Friday May 08, 2026 @07:18AM (#48061532)
I don’t see irony there. We’re locked into CUDA due to past decisions. And in new decisions we don’t want to repeat that mistake.
Re:Mojo 1.0 Beta by pjmlp on Friday May 08, 2026 @12:54PM (#48065719)
CUDA won because AMD and Intel made a mess out of OpenCL, and Khronos had no vision to support anything beyond C99 dialect until it was too late.

Doesn't matter if it was closed, when the alternatives were much worse.

Re:Mojo 1.0 Beta by physicsguy on Friday May 08, 2026 @04:10PM (#48068113)
Plus NVIDIA clocked that it was also the developer library ecosystem and even now there just aren’t equivalents. The AMD rocFFT library wasn’t even complete compared to FFTW until very recently and cuFFT did that more than a decade ago
Re:Mojo 1.0 Beta by zozbot234 on Friday May 08, 2026 @01:07PM (#48065925)
SYCL is the de facto successor to OpenCL that supports higher level languages. So the vision was and is there.
Re:Mojo 1.0 Beta by pjmlp on Friday May 08, 2026 @01:11PM (#48065989)
As mentioned, Khronos only changed their mind when it was too late.

I can also recite the whole story, the missteps in OpenCL 2. , OpenCL C++, the OpenCL 3.0 reboot, how SYCL came to, CodePlay only proper available implementation, Intel acquisition of CodePlay and everything else.

Re:Mojo 1.0 Beta by MohamedMabrouk on Friday May 08, 2026 @04:36AM (#48060344)
I think that plan is to open source the compiler with 1.0 which is expected to be this summer. so in ~3-4 months time.
Re:Mojo 1.0 Beta by ktm5j on Friday May 08, 2026 @01:06PM (#48065915)
I'm really not sure that's true.. I can't think of a single Python dev I've worked with who cared about opensource. All they cared about is the language being easy and free to use.
Re:Mojo 1.0 Beta by physicsguy on Friday May 08, 2026 @04:09PM (#48068089)
The people that write the libraries care, why do you think Python is where we’re writing ML code and not MATLAB?
Re:Mojo 1.0 Beta by IshKebab on Friday May 08, 2026 @05:13PM (#48068844)
Because MATLAB isn't free to use...

(Among other reasons, but that's easily the main one.)

Re:Mojo 1.0 Beta by physicsguy on Saturday May 09, 2026 @04:15AM (#48073035)
Most of the scientific libraries of note originate in academia where MATLAB is effectively free to users. The cross over to Python was well under way by ~2014
Re:Mojo 1.0 Beta by zbentley on Friday May 08, 2026 @05:14PM (#48068855)
Mojo is free, though. MATLAB costing money is a bigger issue than it being closed source. R was too late to the game and catered too much to professional math/stats/datascience people rather than programming generalists. Python (with native code interop) hit the sweet spot for breadth/accessibility to the market and capability.
Re:Mojo 1.0 Beta by flakiness on Friday May 08, 2026 @01:13PM (#48066020)
https://mojolang.org/docs/roadmap/#contributing-to-mojo

> We're committed to open-sourcing all of Mojo, but the language is still very young and we believe a tight-knit group of engineers with a common vision moves faster than a community-driven effort. So we will continue to plan and prioritize the Mojo roadmap within Modular until more of its internal architecture is fleshed out.

I hope they stick to their original promise. And the 1.0 release would be a great time to deliver this.

Re:Mojo 1.0 Beta by chrislattner on Friday May 08, 2026 @04:11PM (#48068126)
Indeed, this fall 100%
Re:Mojo 1.0 Beta by nextaccountic on Saturday May 09, 2026 @12:21AM (#48071803)
Why didn't you just do this the sqlite way, and open source this, some time ago?

Release the source, but don't take code from external contributors. Take issues and discussion instead

Re:Mojo 1.0 Beta by bmandale on Friday May 08, 2026 @02:16PM (#48066808)
open source does not mean open community. you can just throw tarballs over the wall
Re:Mojo 1.0 Beta by adamnemecek on Friday May 08, 2026 @01:14PM (#48066034)
This is exactly how the open sourcing of Swift went so I imagine it will be the same.
Re:Mojo 1.0 Beta by otabdeveloper4 on Friday May 08, 2026 @01:39PM (#48066339)
> We're committed to open-sourcing all of Mojo

Translated from corporatese it means "it will never happen".

Re:Mojo 1.0 Beta by jlundberg on Friday May 08, 2026 @02:38PM (#48067036)
With Chris Lattners track record, there is little reason to doubt they actually will open source this.
Re:Mojo 1.0 Beta by ModernMech on Friday May 08, 2026 @02:52PM (#48067193)
It’s not Chris Lattner who gets to make the call though. He has investors to the tune of $300 million, and making them happy is the reason it hasn’t been done yet. A lot of people, very reasonably, relieve it’s not possible to satisfy them and also the development community, and when when push comes to shove it’ll be the investors who win because they have the money. So it’s not Chris Lattner’s track record that makes people worried — it’s the track record of investors choosing control over openness, which is a pretty solid record.
Re:Mojo 1.0 Beta by MohamedMabrouk on Friday May 08, 2026 @03:11PM (#48067399)
how is it in investors self interest to keep a programming language (some thing which no one makes money on today) closed? It also means that library authors can't reason about their code well enough because they don't know the language internals, this also hurts ecosystem growth. Their is no money to be made with a closed language that no body uses. probably modular investors know this.
Re:Mojo 1.0 Beta by otabdeveloper4 on Saturday May 09, 2026 @03:33AM (#48072778)
"We're committed" in official speech means "this thing has absolute lowest priority".
Re:Mojo 1.0 Beta by sidkshatriya on Saturday May 09, 2026 @02:02AM (#48072242)
> but the language is still very young and we believe a tight-knit group of engineers with a common vision moves faster than a community-driven effort.

This is a false dichotomy.

For years Golang was developed in the open but strictly moved on the vision of its creators rather than being "community-driven". Many other venerable open source projects don't involve the community in serious strategy discussions. The community mainly acts as a bug finder/fixer. Mojo could do the same: be open source but choose its own priorities internally.

I'm guessing that Mojo is still looking for a monetization strategy. Keeping important things proprietary in Mojo at this stage helps I'm sure (nothing wrong with that).

But I feel the era of proprietary programming language play is over. Unless you create some hardware (which the Mojo guys don't) it's going to be tough.

Re:Mojo 1.0 Beta by melodyogonna on Monday May 11, 2026 @11:07AM (#48096016)
Golang was closed for the first 2 years of its development.
Re:Mojo 1.0 Beta by sureglymop on Friday May 08, 2026 @04:20AM (#48060226)
Mojo is cool but I just don't understand the python backwards compat thing. They're holding themselves back with that.

All the flaws I can think of in Kotlin are due to the Java compatibility. They could've made it work here by being more explicit but the way it currently works seems doomed.

Re:Mojo 1.0 Beta by pjmlp on Friday May 08, 2026 @08:05AM (#48061894)
Same story with C and Objective-C, C and C++, JavaScript and TypeScript, Java and Scala, Java and Clojure,.....

Yes the underlying platform they based their compatibility on, is the reason they got some design flaws, some more than other.

However that compatibility is the reason they won wide adoption in first place.

Re:Mojo 1.0 Beta by tasuki on Friday May 08, 2026 @07:38AM (#48061684)
They coulda made it Scala!
Re:Mojo 1.0 Beta by geodel on Friday May 08, 2026 @01:00PM (#48065816)
> All the flaws I can think of in Kotlin are due to the Java compatibility.

All the use of Kotlin in industry are due to Java compatibility. Else there would be ~0% marketshare of Kotlin.

Re:Mojo 1.0 Beta by loglog on Friday May 08, 2026 @03:36PM (#48067699)
Mojo is NOT Python compatible (although they initially wanted it to be). So they got all downsides without the upsides.
Re:Mojo 1.0 Beta by fiedzia on Friday May 08, 2026 @08:28PM (#48070472)
They claim you can easily mix them so there is some degree of compatibility.
Re:Mojo 1.0 Beta by Conscat on Friday May 08, 2026 @11:47PM (#48071639)
Every reasonable language has a Python interop story. All it takes is C FFI. But what Mojo promised early on was the eventuality of compiling a large amount of Python code if not entire wheels as Mojo.
Re:Mojo 1.0 Beta by melodyogonna on Saturday May 09, 2026 @03:32AM (#48072764)
I don't recall they promised that. They promised it'll be a superset, but Mojo introduces new keyword. Mojo could support all Python features today exactly as they're supported in Python and you wouldn't still be able to copy Python code into Mojo and compile it
Re:Mojo 1.0 Beta by boxed on Saturday May 09, 2026 @01:48AM (#48072167)
"All downsides"? What do you mean?
Re:Mojo 1.0 Beta by jasonjmcghee on Friday May 08, 2026 @04:29PM (#48068385)
There is unfortunately likely a lot of truth to this. I like Kotlin, but, anecdotally, I've only ever chosen it due to needing JVM
Re:Mojo 1.0 Beta by davidatbu on Friday May 08, 2026 @01:32PM (#48066260)
I'm pretty sure that they have decided that backwards-compat is not the best path for Mojo. Matter of fact, the following is the _last_ item on the roadmap on the home page:

> Supporting more of Python's dynamic features like classes, inheritance, and untyped variables to maximize compatibility with Python code.

What's more, note how it says "to maximize compatibility" not "to achieve full compatibility."

Re:Mojo 1.0 Beta by boxed on Saturday May 09, 2026 @01:46AM (#48072155)
> Mojo is cool but I just don't understand the python backwards compat thing. They're holding themselves back with that.

In reality I think they've dropped that pretty hard. Literally you can't even get the length of a string with `len(s)` in the latest release. They also removed negative indexing, which I find baffling and frustrating. The roadmap does say they don't intend to have any "syntax sugar" until later in the implementation, but negative indexing is such a core part of what makes Python so much nicer to work with compared to say C++...

Re:Mojo 1.0 Beta by digdugdirk on Friday May 08, 2026 @02:08PM (#48066723)
It does almost seem like they're trying to recreate the Nim programming language in this regard.
Re:Mojo 1.0 Beta by rao-v on Friday May 08, 2026 @07:28PM (#48070038)
I still don’t understand why we lack a language that will take uncomplicated computation heavy code and turn it into SIMD / multi thread / multiprocessing / GPU code with minimal additional syntax.

Surely this is the sort of thing compiler / language design nerds dream about?

It doesn’t have to guarantee efficiency or provide cutting edge performance in any context … it should just exist!

My understanding is that we can make such a language … but it’s not caught the fancy of someone who could do it

Re:Mojo 1.0 Beta by oldmanhorton on Friday May 08, 2026 @07:47PM (#48070167)
Both ahead of time compilers and JIT compilers often perform autovectorization of tight loops. The problem is that lots of hot loops are not necessarily simple loops, and in particular a lot of source code is written in a way which uses sequential dependencies that can’t be modeled in SIMD code. Aside from undefined behavior in C/C++, most compilers will fail to autovectorize because doing so would very slightly change the behavior of your code in a very hard to understand way.
Re:Mojo 1.0 Beta by rao-v on Friday May 08, 2026 @08:47PM (#48070616)
Surely a high level language can own the contract of making sane choices of when to auto vectorize and when not to (or just inefficiently auto vectorize - that is fine too!)
Re:Mojo 1.0 Beta by throwup238 on Friday May 08, 2026 @10:44PM (#48071283)
That’s like saying “surely a high level language can solve the halting problem.”

Yes, it can, but only by eliminating the features that make it Turing complete. It’s relatively easy to vectorize map with a closure that can’t mutate anything but once you have nontrivial control flow, the compiler can’t make those kinds of assumptions.

Re:Mojo 1.0 Beta by rao-v on Saturday May 09, 2026 @12:32AM (#48071846)
It’s really not! We’re not requiring the language to make optimal choices, just that it convert the same code to these different paradigms (and honestly you could just brute force run the 12 versions and choose the fastest one). Absolutely no theory barriers apply!
Re:Mojo 1.0 Beta by bobbyswiss on Saturday May 09, 2026 @05:14AM (#48073398)
You should design it!
Re:Mojo 1.0 Beta by rao-v on Saturday May 09, 2026 @01:14PM (#48076514)
Some kind soul pointed to Intel’s https://ispc.github.io/ which is basically this.

Missing some features but roughly has the idea. Keep faith with human ingenuity!

Re:Mojo 1.0 Beta by JBits on Friday May 08, 2026 @07:46PM (#48070160)
If you're happy with NumPy's API, then surely JAX is exactly what you're looking for.
Re:Mojo 1.0 Beta by rao-v on Friday May 08, 2026 @08:45PM (#48070602)
JAX can’t do what Numba can do for example. I just want one way to write simple math-y code like you normally would and automagically convert to run on one of the above approaches.

That’s what compilers and high level languages are supposed to be for!

Re:Mojo 1.0 Beta by teleforce on Friday May 08, 2026 @09:20PM (#48070805)
>I still don’t understand why we lack a language that will take uncomplicated computation heavy code and turn it into SIMD / multi thread / multiprocessing / GPU code with minimal additional syntax.

It's already (partly) existed called D language, by default it's garbage collected (GC), can also be program without it or hybrid. It's a modern, backward compatible with C and it's included in GCC.

The linear algebra system in D or Mir GLAS is standalone BLAS implementation written directly in D [1]. It's already proven faster than the other widely existing conventional BLAS like OpenBLAS back in 2016, about ten years ago!

This popular OpenBLAS include Fortran based LAPACK (yes you read it right Fortran) and it is being used by almost all data processing languages currently Matlab, Julia, Rust and also Mojo [2].

Interestingly there is a very early stage of standalone BLAS implementation written directly in Mojo namely mojoBLAS similar to Mir GLAS just started very recently [3].

>Surely this is the sort of thing compiler / language design nerds dream about?

You can say this again.

Especially on the GC side of the programming language since this SIMD / multi thread / multiprocessing / GPU can be abstracted away.

Actually someone recently proposed VGC or virtualized garbage collector for Python in C++ for heteregenous GC [4],[5]. However, the current evaluation excludes JIT compilation, AOT optimization, SIMD acceleration, and GPU offloading.

[1] OpenBLAS:

https://en.wikipedia.org/wiki/OpenBLAS

[2] Numeric age for D: Mir GLAS is faster than OpenBLAS and Eigen:

http://blog.mir.dlang.io/glas/benchmark/openblas/2016/09/23/...

[3] mojoBLAS:

https://github.com/shivasankarka/mojoBLAS

[4] Virtual Garbage Collector (VGC): A Zone-Based Garbage Collection Architecture for Python's Parallel Runtime:

https://arxiv.org/abs/2512.23768

[5] VGC-for-arxiv:

https://github.com/Abdullahlab-n/VGC-for-arxiv

Re:Mojo 1.0 Beta by rao-v on Saturday May 09, 2026 @12:30AM (#48071837)
Delightful thank you! Would love to see a version of D that auto vectorizes to Vulkan or something
Re:Mojo 1.0 Beta by MohamedMabrouk on Saturday May 09, 2026 @04:07AM (#48072984)
I don't think mojo depends on OpenBLAS or other BLAS implementation. I remember that they took a lot of pride in the early days how linalg primitives like matmul which was completely written in mojo was faster than MLK, openBLAS and other implementations.
Re:Mojo 1.0 Beta by ilayn on Sunday May 10, 2026 @09:14AM (#48083726)
It does not have to be in Fortran. It's just historical reason. If you want a C version of LAPACK I have one for you https://github.com/ilayn/semicolon-lapack
Re:Mojo 1.0 Beta by tosh on Saturday May 09, 2026 @12:32AM (#48071845)
Still a bit early but I'm working on kiwi, a k-dialect that can lower to Apple MLX.

Currently supports CPU and GPU on macOS and CPU on linux.

https://kiwilang.com

https://github.com/kiwi-array-lang/kiwi

Kiwi runs computations on small dense arrays in its own runtime, when they are larger it will lower to MLX CPU and eventually to MLX GPU when it is worth it.

As user you don't have to change any code, you just write k.

I'm sure there are other languages designed to take advantage of modern GPUs.

But even with SIMD you can get quite far with array oriented code and many array language implementations will make use of it (BQN, ngn/growler/k, goal, ktye k has a version with SIMD support, …)

Re:Mojo 1.0 Beta by rao-v on Saturday May 09, 2026 @12:59AM (#48071958)
Thanks for sharing this is neat!

I’ve yet to find a language that does SIMD / multithreading / GPU with minimal tweaks let along multiprocessing.

Re:Mojo 1.0 Beta by mappu on Saturday May 09, 2026 @01:38AM (#48072118)
Intel Ispc is a compiler for a C superset language that targets CPU SIMD and GPUs.
Re:Mojo 1.0 Beta by rao-v on Saturday May 09, 2026 @02:11AM (#48072307)
A beautiful find! It’s what 12+ years old at this point?

Definitely the closest thing so far (doesn’t do multiprocessing) but does seem to do SIMD / multithreading and GPU auto parallelizing!

Any idea why it’s so little known?

Re:Mojo 1.0 Beta by QuadmasterXLII on Saturday May 09, 2026 @09:31AM (#48074824)
julia StaticCompiler.jl is the closest to doing this but its buggy, the error messages are terrible, theres no documentation and its ambiguous whether its still in development. but ive looked, nothing better exists.
Re:Mojo 1.0 Beta by rao-v on Saturday May 09, 2026 @01:19PM (#48076559)
I’ll check it out!

https://ispc.github.io/ Also seems promising