Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mojo is now open source

modular.com

Post reply on HN
Print view View original

61–70 of 108 posts

Re: Mojo is now open source

#61

Post by [deleted] »

MohamedMabrouk wrote: post #18
vovavili wrote: post #16

Earlier quoted context omitted.

Can't you just use Numpy directly in Mojo?

you can but through a python interpreter in the mojo process so you get the same numpy speed with mojo ptyhon interop overhead. NuMojo is native and also is now starting to support features that numpy can't really do like native GPU execution.

[deleted]

Re: Mojo is now open source

#63

Post by melodyogonna »

branko_d wrote: post #42

Is this a case of of Qualcomm commoditizing their complements? Does Mojo have a potential for disrupting Nvidia's current market position? https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/

I think people underestimate the fact that Nvidia's GPUs are really good. Modular/Qualcomm's stack will provide a lot more optionality, but from what I saw in the Modcon conference on Tuesday, most of the target audience is towards other hardware vendors. At the moment, after designing a new hardware, you'd have to also build the entire software stack already existing on Cuda, ROCm, etc - this can double or triple your hardware bring up time. If you plug into Max (not Mojo), you get most of the software stack for free, so your software bring up time can go from months of engineering hours to probably weeks.

Re: Mojo is now open source

#64

Post by embedding-shape »

Finally, gonna be a lot of fun to finally play around with, lets see how it compares to Python for ML ultimately :) The build process is quite heavy, pinning all my cores at 100% on a Threadripper 9970X for ~15 minutes which isn't so common.

Curious to know what setups they've tested Mojo on so far, as I understood it to be mainly for ML/AI stuff, so commonly pretty beefy workstation, yet I'm getting warnings that it's not recognizing my GPU (RTX Pro 6000). Seems easy enough to work around by editing the gpu_mapping in MODULE.bazel so I guess isn't a huge issue. Just strange to see a really CPU-heavy build, then not recognizing a somewhat common "prosumer" GPU (common in the ecosystem and expected user audience at least).

Re: Mojo is now open source

#65

Post by ipsum2 »

Alien1Being wrote: post #53

"Qualcomm to Acquire Modular 06/24/2026" https://investor.qualcomm.com/news-events/press-releases/new... Can acqui-death be far away...?

Prediction: Chris Lattner will be off chasing some other shiny thing within a year. Without a strong champion, the company will be subsumed into Qualcomm and stop publishing meaningful updates.

Re: Mojo is now open source

#66

Post by melodyogonna »

Alien1Being wrote: post #53

"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

Re: Mojo is now open source

#67

Post by spmurrayzzz »

embedding-shape wrote: post #64

Finally, gonna be a lot of fun to finally play around with, lets see how it compares to Python for ML ultimately :) The build process is quite heavy, pinning all my cores at 100% on a Threadripper 9970X for ~15 minutes which isn't so common. Curious to know what setups they've tested Mojo on so far, as I understood it to be mainly for ML/AI stuff, so commonly pretty beefy workstation, yet I'm getting warnings that it…

My expectation is always that sm120 is the forgotten orphan in the mix and that I'll have to monkey-patch my way to getting things running (and its not always due to lack of tcgen05 or other "real blackwell" features, its often just failing fallback kernel paths doing things that were clearly not tested).

Mojo's design goals would in theory help this problem long term, but my sm120 PTSD still lingers.

Re: Mojo is now open source

#68

Post by pjmlp »

anonreplier wrote: post #57
pjmlp wrote: post #46

Earlier quoted context omitted.

We already could do that with VMWare Workstation and VirtualBox, since at least 2010. WSL could have been avoided if Microsoft had been more serious about the POSIX subsystem in Windows NT, or later Subsystem for UNIX-based Applications that was available until 2016.

> We already could do that with VMWare Workstation and VirtualBox, since at least 2010. Yes but MS obviously viewed it as important enough to bring it inside their ecosystem. As for the POSIX subsystem in NT, MacOS is POSIX compliant but Apple provide virtualization APIs to run Linux.

Because nowadays Linux ABI is more relevant than pure POSIX compliance.

BSDs and all surviving mainframes and micros also have either Linux VM support or syscall compatibility.

Microsoft saw those geeks that were buying Apple as shinny Linux, and then complaining about lack of compatibility, or that they only cared about POSIX toys but not really Linux proper, and saw a business case in shipping Linux in the box to counter that.

Which had they kept and improved POSIX support since Windows NT 3.51, that would never been a matter to discuss about.

Re: Mojo is now open source

#70

Post by insane_dreamer »

MohamedMabrouk wrote: post #18
vovavili wrote: post #16

Earlier quoted context omitted.

Can't you just use Numpy directly in Mojo?

you can but through a python interpreter in the mojo process so you get the same numpy speed with mojo ptyhon interop overhead. NuMojo is native and also is now starting to support features that numpy can't really do like native GPU execution.

> features that numpy can't really do like native GPU execution

we use numpy + jax for that; works well

Post reply on HN