Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by mjt0229 on Tuesday August 20, 2013 @04:03PM
(#6246155)
I'm interested in this, but why not just write natively in Scheme? I really like Clojure, but if you don't need the Java interop, Scheme seems just as nice.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by olenhad on Tuesday August 20, 2013 @04:18PM
(#6246261)
Scheme is great, but I think there are several key features that clojure has that scheme doesn't provide by default, including (but not limited to):
- Persistent Hash-Trie based Data Structures
- Beautiful asynchronous constructs
- Multimethods
- Protocols
Obviously I in no way intend to discredit scheme, nor start a lisp flamewar :)
/sidenote I love this article comparing a game written in 4 lisp dialects (http://technomancy.us/169)
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by slyrus on Tuesday August 20, 2013 @04:40PM
(#6246399)
For one thing, one might get interoperability with clojure libraries (at least those that aren't just wrappers around java libraries). For another thing, clojure has some nice language features and I'm all for supporting multiple lispy dialects on top of various compiler/runtime environments. My personal wish is to have clojure running on SBCL with trivial interoperability between common lisp and clojure code.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by wes-exp on Tuesday August 20, 2013 @06:09PM
(#6246927)
Clojure running on SBCL seems like a no-brainer. I do not know why this does not exist. SBCL is super high-performance and the underlying lisp semantics should be a perfect fit.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by rsanders on Tuesday August 20, 2013 @09:52PM
(#6247708)
Clojure is intended to be a hosted language. Building on and providing first class access to a rich ecosystem of libraries and tools was an explicit goal.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by DigitalJack on Tuesday August 20, 2013 @05:51PM
(#6246829)
Clojure was initially implemented on cl. You should be able to find the lisp version in the history of the repo somewhere. Might be an interesting starting point.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by mjt0229 on Tuesday August 20, 2013 @04:22PM
(#6246288)
Certainly. As I said, I like Clojure, but I'd be happy to be able to program in Scheme as well. I guess the history of LISP should have told me that not all people who like one LISP necessarily don't mind using another.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by takeoutweight on Tuesday August 20, 2013 @04:13PM
(#6246235)
Clojure has a much stronger polymorphism story than Scheme. This makes sense as Clojure was designed to live in an OO host language. Practically this could mean, say, much cleaner Objective-C interop.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by bitsai on Tuesday August 20, 2013 @03:30PM
(#6246002)
Fascinating! We use Clojure heavily, but the JVM is sometimes a bit of a headache-inducer in our environment (especially w.r.t. its eager gobbling of memory), so I'm always excited to see new potential runtimes/backends for Clojure.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by jlongster on Tuesday August 20, 2013 @04:19PM
(#6246270)
I love it when several incredible technologies come together to allow things you wouldn't think possible. Take this thing over there, stir in some of that, and boom, you've got a working project that is crazy full of potential. Great work Nathan.
Really, when I think about it, it's why I love the world of programming.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by roryokane on Tuesday August 20, 2013 @10:47PM
(#6247868)
I don’t know much Clojure, but I thought that lack of TCO was not a problem because you can just manually add `recur` (http://clojure.org/special_forms#Special%20Forms--%28recur%2...) when you need it. Are there situations where `recur` doesn’t work but tail-call optimization would help?
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by takeoutweight on Tuesday August 20, 2013 @11:00PM
(#6247919)
In my talk I use a finite state machine as an example of something that can really benefit from proper tail calls. In this case, the difference between proper tail calls and loop/recur is the difference between "compiling" the FSM and running the FSM in an interpreter loop.
Re:Clojure-scheme: Compiling Clojure to Native Code via Sche...
by moomin on Tuesday August 20, 2013 @07:16PM
(#6247229)
Also in this space is Tim Baldridge's mjolnir project, which generates native code directly from Clojure using LLVM. It looks very promising, although there haven't been any commits in the last few months.
- Persistent Hash-Trie based Data Structures
- Beautiful asynchronous constructs
- Multimethods
- Protocols
Obviously I in no way intend to discredit scheme, nor start a lisp flamewar :) /sidenote I love this article comparing a game written in 4 lisp dialects (http://technomancy.us/169)
Rich originally made two other JVM/lisp hybrids, one was running java code inside CL, the other was CL on the JVM. [1]
Clojure originally targeted the JVM and CLR, but AFAIK, one of the main motivators was always to run on a major platform.
http://sourceforge.net/projects/jfli/
One was a Lisp(Works) FFI to Java (jfli) and the other was a generalized version of that (foil).
I have seen too the early sketch of Clojure in CL.
Look here: http://clojure.googlecode.com/svn-history/r454/trunk/src/lis...
I didn't realize there was a CL version of the compiler, cool! Thanks for the link.
Really? I thought Clojure evolved out of Rich's never-finished CL-subset-on-JVM implementation.
It's also of course debatable that scheme is "just as nice", so you can imagine there are people who, other things being equal, prefer Clojure.
Many Schemes have their own OO implementations and they all support polymorphism.
https://github.com/schani/clojurec
Really, when I think about it, it's why I love the world of programming.