Hacker News Reader

Comment by masijo | Hacker News Reader

>If someone could give me the ergonomics of Clojure, but without the JVM and the ability to easily target 1/ native (incl easy bidirectional C iterop), 2/ wasm, and 3/ support both in aot and runtime + JIT modes, I would switch in a heartbeat.

Might want to look at Jank (https://jank-lang.org/, https://github.com/jank-lang/jank). It's still in it's early stages but it's basically all you're hoping for!

View on HN

The name might be hard to push to management, but I love that it is s-expr based.

I'll definitely check it out, but if you don't mind me asking: how good is the REPL side on Jank? If it is remotely close to SBCL, then I might become a fan.

jank will have full nREPL support, so the REPL story should be at parity with Clojure. I'm working on the nREPL server now We're JIT compiling C++ code, so there are indeed more dragons.

Hi,

Late to the party, do you think you could give me a comparison of Jank vs Janet ? I'm just starting to look at janet, and just found out about jank at this point.

How usable is Jank for greenfield projects, The comparison page isnt that useful as I don't know what I'm missing.

Thanks in advance.

In terms of design, Janet is Clojure-inspired, but very much does its own thing. jank is a Clojure, such that any existing Clojure code you have will work. Largely speaking, only Java intorop needs to be ported, using a reader conditonal.

Beyond that, jank is built on a C++ host and interops with C++. This means you qan use C++ features, such as templates, in your jank code. Janet has a C runtime and any C++ interop will need to be through C's ABI.

Lastly, Janet is usable today while jank is still under heavy development.

Will check it out!

Reply on news.ycombinator.com