The Next Big Step in Mojo Open Source • Hacker News Board

Re: The Next Big Step in Mojo Open Source

#21

Post by vineyardmike » Fri, Mar 29, 2024, 4:27 AM UTC

CurriedLambda wrote: post #15

Is anyone else surprised at the straightforward collections implementations? From reading this site (and leetcode interviews) I expected to find advanced data structures under the hood. This is not a negative comment, I'm pro Mojo, just wondering who the heck is using the fancy stuff we get quizzed on in interviews if not stdlib devs.

They're used only as needed. Which is to say, rarely.

Eg. A database might store its index in a B-Tree, or other "similar" data structure. For example, you can see RocksDB using "fancy" structure to store its data [0].

[0] https://github.com/facebook/rocksdb

Re: The Next Big Step in Mojo Open Source

#22

Post by bitwalker » Fri, Mar 29, 2024, 4:58 AM UTC

Pretty disappointed to not find sources for the compiler yet, which is the part I'm by far the most interested in. Hopefully that will follow this release soon!

Re: The Next Big Step in Mojo Open Source

#23

Post by modernerd » Fri, Mar 29, 2024, 6:16 AM UTC

ptx wrote: post #16

modernerd wrote: post #7

Mojo feels like a great fit for so many domains outside of AI. It could be a killer general purpose language. It's easy to read and write, offers memory safety without RC or GC or even much mental overhead, will (eventually) be a superset of Python, and it's very performant already. So far I've been hesitant to invest more time in it when it's pitched as "the programming language for all AI developers", when it's dis…

The memory management approach is basically the same as in Rust, according to the docs[0]. Merging Rust and Python into a single language sounds like a very challenging project, with "eventually" being far into the future at best. [0] https://docs.modular.com/mojo/manual/values/ownership

Right, but with improved ergonomics that make Mojo easier to learn and write than Rust, the biggest difference being “borrow by default” as described here:

https://www.modular.com/blog/mojo-vs-rust-is-mojo-faster-tha...

Re: The Next Big Step in Mojo Open Source

#24

Post by aconz2 » Fri, Mar 29, 2024, 1:09 PM UTC

What is the deal with exceptions? I see https://docs.modular.com/mojo/roadmap#the-standard-library-h... and https://github.com/modularml/mojo/blob/main/stdlib/src/built... but then other places debug_assert is used https://github.com/modularml/mojo/blob/6d2a7b552769358ec68a9...

Re: The Next Big Step in Mojo Open Source

#25

Post by jarbus » Fri, Mar 29, 2024, 3:50 PM UTC

If people from the Mojo team are here, I’m curious what the arguments were against focusing on improving the Julia ecosystem and instead building Mojo? Julia solves the multi-language problem pretty well now and already has lots of great ML libraries that could use greater support.

Edit: nevermind, realizing from the a YouTube video linked in the comments that they viewed Python compatibility as a non negotiable