Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
1–10 of 37 posts
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#2I REALLY want to use mojo...but they still don't have basic backwards compatibility features like lambda done. I worry mojo won't get off the ground because they're too focused on hardware performance and aren't building enough features to justify the switch... to get that hardware performance.
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#3It's fashionable to hate on Mojo, but I actually hope they succeed. I started my career by writing fast, production-grade replacements for Python programs written by scientists. Without someone like me, they were squandering government-funded compute resources and wasting time on the critical path to delivering their scientific contributions.
Any technological advancement that gets them more efficiency and leverage without the bottleneck of working with a software engineer would both empower scientists and free up software engineers for other problems.
It remains to be seen whether it will actually deliver on this potential. I think a lot has been promised before it's been proven. But I do think something like this is worth attempting and thoughtful work is being applied to the attempt.
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#4Heard some positive things about Mojo. But my curiousity waned after I learnt it was not open source currently.
In 2024 why should I be interested in a language that is not open source ? Perhaps I'm missing something ?
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#5So how is Mojo comparing with Hylo (formerly Val), the other former Swift creator created new language?
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#6Heard some positive things about Mojo. But my curiousity waned after I learnt it was not open source currently. In 2024 why should I be interested in a language that is not open source ? Perhaps I'm missing something ?
The standard library is open source, you can find it here: https://github.com/modularml/mojo/tree/nightly/stdlib
We'll be opening up more over time - stay tuned!
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#7Mojo feels like a language that's trying to be everything for everyone.
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#8I am really enjoying the language, the level of improvement over the last few months has been amazing. At work all our heterogeneous compute needs are implemented using C++/CUDA. I've been exploring new languages for the type of work we do on and off over the last few years: Julia, Rust, D, Chapel, and Mojo.
It seems the only new languages serious about native heterogeneous compute are: Julia, Chapel, and Mojo.
Of those languages I can say Mojo and Chapel were the most impressive. But Mojo is just so fun to write, I've ported a bunch of my "hobby numerical code" to Mojo. I am practically all in on Mojo since it'll give me access to MLIR.
I have always wondered though, why does Chapel get no love online???
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#9Mojo feels like a language that's trying to be everything for everyone.
I feel the opposite, they really are focused on being a language that's great for AI and heterogeneous compute, since that's what Modular is focused on. But the features are attractive for other use cases, it has access to MLIR, compile time metaprogramming, easy and ergonomic SIMD, and soon GPU support.
Re: Mojo: Ownership and lifetime checks deep dive with Chris Lattner [video]
#10Heard some positive things about Mojo. But my curiousity waned after I learnt it was not open source currently. In 2024 why should I be interested in a language that is not open source ? Perhaps I'm missing something ?
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.