4 ms·

I'm glad that it's open source now and they are supporting a lot more hardware. There are some interesting features that I hope the language design community pa

I'm glad that it's open source now and they are supporting a lot more hardware. There are some interesting features that I hope the language design community pays attention to. It's built on top of MLIR so you can make compiler optimizations in a library instead of the compiler. I believe Reactant.jl has been using MLIR for optimizing higher level abstractions in Julia. Imagine a Lisp with that capability.

eigenspace 2mo ago
Julia is extremely lispy in its semantics and design, it's mostly separated by syntax.
thimotedupuch 2mo ago
Indeed Reactant looks like a young, fantastic piece of technology.
pjmlp 2mo ago
Julia is a Lisp, just like Dylan or Lisp 2. Many Lisps have that capability.
- eigenspace 2mo ago
  IMO saying julia is literally a lisp is just not worth the type of discussion it generates. I'd much prefer to say the important part: Julia learned a ton of very important lessons from the lisp family of languages, and has integrated a lot of them.
  - pjmlp 2mo ago
    Agreed.
  - dnautics 1mo ago
    isnt its core literally femtolisp, ehich was written by one of the julia authors?
    - eigenspace 1mo ago
      The parser and lowering passes were in femtolisp, and yes Jeff wrote femtolisp. However, There's now a pure julia implementation of the parser that's on by default, and the julia implementation of lowering is also almost done and ready to replace the femtolisp one. But honestly, these things aren't really what I mean when I say julia is lispy, those are just easter eggs. I more mean the language design and semantics.
adsharma 2mo ago
Mojo as MLIR++ is how I've thought about it as well. Many users will find transpiling static python to mojo an interesting path. Updating py2many --mojo to 1.0 to see what breaks. Also looking forward to translating existing python adt module to mojo Variant in phase 2. I hope the mojo pattern matching proposal looks more like rust (expression) and not like python (statement).

eigenspace 2mo ago

Julia is extremely lispy in its semantics and design, it's mostly separated by syntax.

thimotedupuch 2mo ago

Indeed Reactant looks like a young, fantastic piece of technology.

pjmlp 2mo ago

Julia is a Lisp, just like Dylan or Lisp 2. Many Lisps have that capability.

eigenspace 2mo ago
IMO saying julia is literally a lisp is just not worth the type of discussion it generates. I'd much prefer to say the important part: Julia learned a ton of very important lessons from the lisp family of languages, and has integrated a lot of them.
- pjmlp 2mo ago
  Agreed.
- dnautics 1mo ago
  isnt its core literally femtolisp, ehich was written by one of the julia authors?
  - eigenspace 1mo ago
    The parser and lowering passes were in femtolisp, and yes Jeff wrote femtolisp. However, There's now a pure julia implementation of the parser that's on by default, and the julia implementation of lowering is also almost done and ready to replace the femtolisp one. But honestly, these things aren't really what I mean when I say julia is lispy, those are just easter eggs. I more mean the language design and semantics.

adsharma 2mo ago

Mojo as MLIR++ is how I've thought about it as well. Many users will find transpiling static python to mojo an interesting path. Updating py2many --mojo to 1.0 to see what breaks. Also looking forward to translating existing python adt module to mojo Variant in phase 2. I hope the mojo pattern matching proposal looks more like rust (expression) and not like python (statement).