4 ms·
I think the article should be titled 'JVM isn't for me'. According to the article, the author moved to Janet, because it is Clojure-like without the JVM overhe
by delegate 4y ago
I think the article should be titled 'JVM isn't for me'.
According to the article, the author moved to Janet, because it is Clojure-like without the JVM overhead.
- jcadam 4y agoI think the JVM route is smart for bootstrapping a new language since it gives you an existing ecosystem to leverage. However, at this point, I'd love to see a native Clojure.
- pjmlp 4y agoThere is already Common Lisp and Scheme for that.
- aidenn0 4y agoRich Hickey was already using a native lisp; then he wrote a couple of bridges between it and JVM/CLR before deciding running a lisp directly on the runtime VM was the way to go.
- petre 4y agoYup, Gerbil Scheme is also bootstrapped on Gambit Scheme. And Racket uses Chez Scheme underneath.
- swlkr 4y agoFair enough, I usually start with the title and try to let the rest flow from there, but it's definitely the JVM that was getting me down, not clojure specifically.
- jmchuster 4y agoHow about Clojure on node? Starts and runs instantly https://planck-repl.org/ https://planck-repl.org/
- swlkr 4y agoYes, the newer clojure runtimes like planck or native-image, or babashka definitely take away some of the jvm pain
- nesarkvechnep 4y agoWhy not Lisp on the BEAM - https://lfe.io/ https://lfe.io/.
- crispyalmond 4y agoI prefer to use nbb[0] for this, or babashka[1] when I need to use stuff specific to JVM. [0]: https://github.com/babashka/nbb https://github.com/babashka/nbb [1]: https://babashka.org/ https://babashka.org/
- petre 4y agoJanet was kind if slow when I tried it and it's too different compared to Clojure. I think I'll stick to Racket for playing with Lisps.