Am I understanding the current state of things correct?
(And now in the age of LLMs, the barriers to get started with a new programming language are lower than ever)
Much better options out there. Python already has libraries like Pydantic that offload performance to functions written in Rust under the hood.
Hmm, I've been under the impression that at one point they said it'd be 100% FOSS by the time 1.0 hits, but maybe I misunderstand/misremember the details. But I remember they'd said it'd be FOSS in connection with 1.0, seems weird to do it this way instead of waiting until it's all FOSS then cut 1.0.
But I hope they succeed, it's a very interesting approach. Then I will jump on it later on. S
They should show some performance comparisions between PyTorch and Mojo, PyTorch+kernel compilation + Triton vs Mojo, ThunderKittens vs Mojo.
The fact that they release 1.0 without doing this, I think says a lot. I personally haven't even started looking into Mojo because of the closed source stuff, but usually you can tell what's going on by looking for what's obviously missing.
Lastest OpenCV 5 release notes also had a lot of LLMisms.
I guess that's the new normal. Still, I am very hopeful for Mojo.
Did they think that image would make them look fun or interesting? Because it's exactly the opposite.
Why not now though? Why wait for 4 more months? What magic is there to hide in just making it source available at least.
Clang actually has replaced most GCC forks exactly because vendors can keep the fork closed source.
melodyogonna•2h ago