News for hackers. Stuff that matters.
Re:Mojo: Ownership and lifetime checks deep dive with Chris ... by loudmax on Monday May 13, 2024 @02:31PM (#40346615)
Mojo's developers claim that they intend for Mojo to be open source: https://www.modular.com/blog/the-next-big-step-in-mojo-open-...

This is encouraging, and it seems that at least the core of the language is now open: https://github.com/modularml/mojo

I haven't tried it and I don't have a sense of how open Mojo really is today, or what's left that isn't open. I tend to agree that we should take the open source claim with skepticism until we see it in action.

The goals for the project are promising: something like the expressiveness of Python combined with the speed and safety of Rust. If they can pull it off, and it's open source, that will be very impressive.

Re:Mojo: Ownership and lifetime checks deep dive with Chris ... by archargelod on Monday May 13, 2024 @07:30PM (#40349807)
> something like the expressiveness of Python combined with the speed and safety of Rust.

Isn't that problem already solved? We already have Nim[0] that is memory-safe language with Python-esque syntax and performance of C. Yeah, it's not an extension of Python as Mojo claims to be; but I'd pick a mature language with proven design for my projects over something that's not even out yet.

[0]- http://nim-lang.org

Re:Mojo: Ownership and lifetime checks deep dive with Chris ... by Maxatar on Monday May 13, 2024 @09:14PM (#40350519)
Nim is not memory safe and doesn't technically claim to be. What they claim is to provide memory safe features, but then so does C++ and a lot of other languages.
Re:Mojo: Ownership and lifetime checks deep dive with Chris ... by ivell on Tuesday May 14, 2024 @12:47AM (#40351696)
I didn't understand what you meant. Nim has GC by default. It does support pointers, but then Rust does too.