Skip to content

Comment on Coast on Clojureparent

Comments

Id actually love to hear what made you move on, if you have a few minutes to spare!

He wrote a blog post about it https://swlkr.com/posts/clojure-isnt-for-me/

TLDR: He hated the Java part of Clojure

Yeah that’s the long and short of it.

I spent a lot of time in jvm land though, a few years of nights and weekends, but I finally learned that it wasn’t for me.

I’m a C (or rust or llvm or what have you, wasm?) person, not a jvm person.

Tried GraalVM?

I’ve tried graal and native-image, both are awesome.

clojure still relies on the jvm though, for repl things.

sci and babashka were interesting, but at that point I had already moved on to janet

Ja that is always like a little splinter in my brain as well. I hope I don't bring out the language-wars but I always wanted a Clojure-Like but with Golang. :) I just love the go ecosystem and statistically compiled binary ! You shipping one binary ! :) No need to edit XML files and "tune java servers"

Again, this is just my preference. YMMYV

There are a few projects that try todo this like this one: https://github.com/mattn/golisp

But it seems abandoned.

I keep staring projects like this, but I haven't found the right level to put a lisp in the Go stack.

I've done a runtime lisp, but it felt like programming a lisp isolated from everything that made Go, well, Go. I've done a simple lisp to generate Go AST to do codegen pre-1.18, but that's not a complete program.

I haven't found the place yet that feels quite like Clojure.

there is joker https://github.com/candid82/joker but you may as well use the small clojure interpreter instead

The x86 monoculture has shaken around a bit. But surprisingly it seems there has been friction even on the JVM side, partly because of Docker style nonportable containers had time to cement in the x86 monoculture period.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.