71–80 of 108 posts
Earlier quoted context omitted.
Showing your ignorance regarding Java and C# ecosystems and available compilers on that reply.
I indeed don't know about Java, but with C# there are a lot of limitations if you want AOT compilation and you still get the bloated binary and limited performance. I also, personally, never seen a single project written in either Java or C# that distributes aot binaries.
At least according to my small experiment:
Earlier quoted context omitted.
I don't agree at all with your last paragraph. MATLAB and Julia are lovely for numerics, maths is terse and looks like maths! Mojo is hobbled by choosing Python style syntax, which does not lend itself well to maths. WRT the type system, I agree MATLAB is a mess but Julia's multiple dispatch feels more like maths than any other language I've tried.
What problems do you run into for maths with Python? For linear algebra and ML with Jax/Numpy I find it quite readable.
The way that types interact with methods _feels_ like maths. I.e. you have a method made up of mathematical operators, if you swap out an input, it typically does the natural and correct thing.
"Qualcomm to Acquire Modular 06/24/2026" https://investor.qualcomm.com/news-events/press-releases/new... Can acqui-death be far away...?
Chris Lattner is now Qualcomm's VP of AI Software and Tooling, so he is now responsible for all of Qualcomms AI software. Mojo wouldn't be doing any dying
I'm sure Qualcomm would love him to stick around but suspect that they'll maintain mojo even if he leaves.
I'm in financial engineering and I feel like mojo is definitely the language for that field in the future, especially with the relatively easy python interop for legacy stuff.
Love this intentionality: ” Our open source approach has been deliberate: we’ve found that small and tight-knit design teams (not committees) are the best for finding the “soul” of a language, but that feedback from a broader community is essential to escape an echo chamber. As such, we first open-sourced the Mojo standard library, then released hundreds of thousands of lines of kernel code written in Mojo, tools, an…
Love this intentionality: ” Our open source approach has been deliberate: we’ve found that small and tight-knit design teams (not committees) are the best for finding the “soul” of a language, but that feedback from a broader community is essential to escape an echo chamber. As such, we first open-sourced the Mojo standard library, then released hundreds of thousands of lines of kernel code written in Mojo, tools, an…
I wish they never abandoned the goal of being a true Python superset. That would have been something.
Given that there are so many failed attempts to optimise arbitrary Python code, it was dubious from the start. Furthermore, the documentation completely ignored these challenges and made it clear that Mojo's goal was to compile to MLIR in order to write kernels for machine learning. The first example of Mojo code was a low level matrix multiplication kernel taking advantage of fancy compilation features and the documentation advertised pointers inspired by Rust's move semantics, neither of which are typically considered friendly or relevant to high level programmers.
I used Mojo a while back before LLM laziness kicked in and agents started writing all the code. I didn't know anything about GPU programming and it almost felt dirty how easy it was to get some performant kernels running (5070). Even I could do it. I'm in financial engineering and I feel like mojo is definitely the language for that field in the future, especially with the relatively easy python interop for legacy st…
Love this intentionality: ” Our open source approach has been deliberate: we’ve found that small and tight-knit design teams (not committees) are the best for finding the “soul” of a language, but that feedback from a broader community is essential to escape an echo chamber. As such, we first open-sourced the Mojo standard library, then released hundreds of thousands of lines of kernel code written in Mojo, tools, an…
I wish they never abandoned the goal of being a true Python superset. That would have been something.