Tomorrow I have a presentation concerning my package, but questions about Julia will surely arrive and likely about Mojo. I haven’t tried it, to those who did it (recently), what do you think are the user cases where Julia is a preferable platform and which one where Mojo is ?

On the plus side, Rust is growing in popularity, is more memory safe when it comes to data races and consistently ranks very well on benchmarks even among other statically-typed languages. I am not much of a Rust fan myself due to its complexity and boilerplate but I think what may end up happening …

requires that you do manual memory management Not so true. The Mojo compiler automatically inserts memory release code at the right positions based on ownership rules

Rust and C++ do this automatically, too. C++ just doesn’t have the borrow checker (which makes it both a little easier to get code working and much easier to get code compiling-but-not working in C++ than Rust). Managing memory in languages without GC but that do have some form of scope based reso…

Instead of normal SBRM, where destructor calls are inserted at scope exit, they can insert them earlier, immediately after last use. That means Mojo is very different from C++ and Rust. a minor innovation here It’s also easy to call anything “minor”.

[image] MilkshakeForReal: That means Mojo is very different from C++ and Rust. Freeing earlier is “very different”? Seems like just a matter of removing a semantic guarantee, and then reordering. I think C++ has too many guarantees around allocations and deallocations being considered obser…

Seems like just a matter of removing a semantic guarantee, and then reordering. What about references.

References just safer and more convenient pointers. Compiler Explorer

I’m not asking for the definition but how “free early” could be such a trivial thing to implement while you have references with their own lifetimes.

Track uses of the pointer? LLVM has tons of infrastructure for this. Look at ScalarEvolution, for example. LLVM can track escape (nocapture parameter attribute); obviously if a pointer escapes, you probably shouldn’t move the free earlier.

[image] Elrod: C++ just doesn’t have the borrow checker (which makes it both a little easier to get code working and much easier to get code compiling-but-not working in C++ than Rust). Managing memory in languages without GC but that do have some form of scope based resource management (SBRM, …

Advantages of Julia vs Mojo

Community

Topic		Replies	Views
Did Modular just reinvent Julia? Offtopic mojo	260	30871	November 25, 2023
Why `Mojo` can be so fast? Offtopic mojo	14	12375	May 15, 2023
Merge Python and Julia, i.e. an (unofficial) integration proposal, sort of like the Mojo language Community	24	3930	October 12, 2023
What do we have to attract C++ or other languages' power users to try Julia? Community offtopic	31	1381	August 12, 2025
Claim (false): Julia isn't multiple dispatch but overloading General Usage multidispatch	135	14709	May 20, 2024

Advantages of Julia vs Mojo

Related topics