←back to thread

311 points melodyogonna | 1 comments | | HN request time: 0.251s | source
Show context
chrislattner ◴[] No.45141096[source]
Thank you for all the great interest in the podcast and in Mojo. If you're interested in learning more, Mojo has a FAQ that covers many topics (including "why not make Julia better" :-) here: https://docs.modular.com/mojo/faq/

Mojo also has a bunch of documentation https://docs.modular.com/mojo/ as well as hundreds of thousands of lines of open source code you can check out: https://github.com/modular/modular

The Mojo community is really great, please consider joining, either our discourse forum: https://forum.modular.com/ or discord https://discord.com/invite/modular chat.

-Chris Lattner

replies(5): >>45143004 #>>45143631 #>>45144626 #>>45145313 #>>45146914 #
bsaul ◴[] No.45143004[source]
Fan here.

I watched a lot of your talks about mojo, where you mention how mojo benefits from very advanced compiler technology. But i've never seen you give concret example of this advanced technology. Please, can you write a blog about that, going as deep and hardcore tech as you can ? As i'm not a compiler dev i'll probably understand 20% of it, but hopefully i'll start to get a sense of how advanced the whole thing is.

replies(1): >>45143199 #
melodyogonna ◴[] No.45143199[source]
They've given a talk abut this on the LLVM dev meeting: https://www.youtube.com/watch?v=SEwTjZvy8vw&

They have some fancy tech around compile-time interpreter, mojopkg, and their code generator. They also have a graph compiler (not mentioned in the talk) that can fuse kernels written in Mojo.

replies(2): >>45144168 #>>45195561 #
1. bsaul ◴[] No.45195561[source]
interesting talk. I thought mojo actually had innovations at the IR level as well, but it seems to rely on what chris built at google with MLIR.

Chris mentioned pushing updates to MLIR while working at Mojo, i'd be curious to have a summary what those changes are, because i believe this is where the hard core innovations are happening.