| ▲ | xiphias2 4 hours ago | |
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. | ||
| ▲ | embedding-shape 3 hours ago | parent | next [-] | |
> They should show some performance comparisions between PyTorch and Mojo, PyTorch+kernel compilation + Triton vs Mojo, ThunderKittens vs Mojo. The fact that they release 1.0 without doing this, I think says a lot. I personally haven't even started looking into Mojo because of the closed source stuff, but usually you can tell what's going on by looking for what's obviously missing. | ||
| ▲ | geodel 2 hours ago | parent | prev | next [-] | |
They kind of did. It has a separate website now [1] . All the docs, announcements, roadmap, some comparisons as you asked are there. So they do seem to be working towards separation. | ||
| ▲ | pbronez 3 hours ago | parent | prev | next [-] | |
Aren’t they already separated? Max is an inference runtime, written in Mojolang, which uses the MLIR compiler chain to target diverse accelerator hardware. | ||
| ▲ | adityazero 12 minutes ago | parent | prev [-] | |
[dead] | ||