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

Mojo 1.0

modular.com

Post reply on HN
Print view View original

101–110 of 197 posts

Re: Mojo 1.0

#101

Post by skavi »

afdbcreid wrote: post #68
totalperspectiv wrote: post #58

Earlier quoted context omitted.

Having written a lot of Mojo over the last two year, just for fun, it's a really cool language. Ownership model adjacent to Rust, comptime in the realm of Zig, rich type system, first class SIMD support, etc. Performance wise it's the first language in long time that isn't just an LLVM wrapper. LLVM is still involved, but they are using it differently than say, Rust or Zig. Very excited for Mojo once it's open source…

> Performance wise it's the first language in long time that isn't just an LLVM wrapper Why? Because it uses MLIR? Rust has its own MIR, it's even more not-LLVM-wrapper.

I'd assume Mojo does more complex transformations at the MLIR level than Rust does at its MIR level.

Re: Mojo 1.0

#103

Post by grim_io »

tyre wrote: post #70
steve1977 wrote: post #53

Earlier quoted context omitted.

So, without significant indentation?

Oh nooooo, they fucked it up too. Why would someone make a language that’s whitespace sensitive? It’s confounding.

I never understood this.

What kind of special whitespace requirements do people have?

Re: Mojo 1.0

#105

Post by mohamedkoubaa »

woadwarrior01 wrote: post #47
redlewel wrote: post #6

Don't see the value of using a language with a closed source compiler... Much better options out there. Python already has libraries like Pydantic that offload performance to functions written in Rust under the hood.

The value has already been materialized. They were acquired by Qualcomm for $3.9 billion.

The value has been speculated on. It doesn't mean the value has materialized.

Re: Mojo 1.0

#107

Post by adityazero »

xiphias2 wrote: post #13

Mojo may be interesting to me, but they should really split it from Max, which is some closed stuff I'm not interested in. They should show some performance comparisions between PyTorch and Mojo, PyTorch+kernel compilation + Triton vs Mojo, ThunderKittens vs Mojo.

[dead]

Re: Mojo 1.0

#108

Post by willseth »

twsted wrote: post #77

Nothing but respect for Chris, and I understand why founders take these deals. But an acquihire usually means the product is the part that gets left behind, and that's the part I cared about.

$3.9 billion is not an acquihire!

Re: Mojo 1.0

#109

Post by jibal »

minraws wrote: post #29

> Finally, we will continue to progressively open-source more of the Mojo language, as well as components in MAX that we have built with it. Our commitment remains unchanged – we will open source the Mojo compiler and toolchain in 2026. Why not now though? Why wait for 4 more months? What magic is there to hide in just making it source available at least.

Who said anything about 4 months? Your "logic" seems to be that they are releasing it in 2026 and there are 4 more months in 2026 so they will be releasing it in 4 months. That's obviously flawed thinking. They will probably be releasing it coincident with their August 18 conference.

Re: Mojo 1.0

#110

Post by afdbcreid »

skavi wrote: post #101
afdbcreid wrote: post #68

Earlier quoted context omitted.

> Performance wise it's the first language in long time that isn't just an LLVM wrapper Why? Because it uses MLIR? Rust has its own MIR, it's even more not-LLVM-wrapper.

I'd assume Mojo does more complex transformations at the MLIR level than Rust does at its MIR level.

First, I'm not sure. Rust has MIR optimizations and also other transformations.

But even if yes, MLIR is part of the LLVM project, so it's technically still "just an LLVM wrapper".

Post reply on HN