8 ms·

Don't need all those Java libraries if you've got good FFI with C libraries. Don't need AOT compilation; if you want performance, just stick with regular Cloju

Don't need all those Java libraries if you've got good FFI with C libraries. Don't need AOT compilation; if you want performance, just stick with regular Clojure on the JVM. I'd love to just see a small general-purpose interpreted Clojure (quick start up, small memory footprint, easy access to C libs), even if it lacked concurrency features.

pjmlp 10y ago
For that I fail to see the point of why not use a Scheme or Common Lisp compiler instead.
- KingMob 10y ago
  Yeah, for native executables, CL and Racket are much further ahead.
- branchly2 10y ago
  Thank you. Though I really like having Clojure's: * literal syntax for maps, vectors, sets, and regexes * keywords * clear separation of functional constructs (`for`, `map`, etc.) vs side-effecting ones (`do`, `doall`, `when`). * large standard library of built-in functions, with overall fairly nice naming of things. I've looked at Scheme, but it appears to be missing those things. I think some of them may be provided by srfi's, but upon a quick reading I couldn't make much sense of how to include and use them.
  - nickik 10y ago
    Racket is probably something you should look at. Im not sure it has all these things, but it is also a modern updated Lisp language based on Scheme.
KingMob 10y ago
Lumo (https://github.com/anmonteiro/lumo https://github.com/anmonteiro/lumo) or Planck may fit your requirements, though they lack a C FFI. They're based off ClojureScript/Javascript, and startup way faster than the JVM Clojure. Could probably try the node-ffi library with Lumo. There's the abandoned ClojureC project (https://github.com/schani/clojurec https://github.com/schani/clojurec). There's also JVM-to-native compilers like gcj or ExcelsiorJet. But at the moment, it doesn't seem like there's an established way to do all that.

8 ms·

Don't need all those Java libraries if you've got good FFI with C libraries. Don't need AOT compilation; if you want performance, just stick with regular Cloju

by branchly2 10y ago

pjmlp 10y ago
For that I fail to see the point of why not use a Scheme or Common Lisp compiler instead.
- KingMob 10y ago
  Yeah, for native executables, CL and Racket are much further ahead.
- branchly2 10y ago
  Thank you. Though I really like having Clojure's: * literal syntax for maps, vectors, sets, and regexes * keywords * clear separation of functional constructs (`for`, `map`, etc.) vs side-effecting ones (`do`, `doall`, `when`). * large standard library of built-in functions, with overall fairly nice naming of things. I've looked at Scheme, but it appears to be missing those things. I think some of them may be provided by srfi's, but upon a quick reading I couldn't make much sense of how to include and use them.
  - nickik 10y ago
    Racket is probably something you should look at. Im not sure it has all these things, but it is also a modern updated Lisp language based on Scheme.
KingMob 10y ago
Lumo (https://github.com/anmonteiro/lumo https://github.com/anmonteiro/lumo) or Planck may fit your requirements, though they lack a C FFI. They're based off ClojureScript/Javascript, and startup way faster than the JVM Clojure. Could probably try the node-ffi library with Lumo. There's the abandoned ClojureC project (https://github.com/schani/clojurec https://github.com/schani/clojurec). There's also JVM-to-native compilers like gcj or ExcelsiorJet. But at the moment, it doesn't seem like there's an established way to do all that.