4 ms·
The shameless plugging pays off! One more HN reader converted. :D Check it out, join our Slack, and stay tuned. jank's still under heavy development right now,
by Jeaye 3y ago
The shameless plugging pays off! One more HN reader converted. :D
Check it out, join our Slack, and stay tuned. jank's still under heavy development right now, and not ready for AOC this year, but it's getting close. The blog is the best way to watch the progress: https://jank-lang.org/blog/ https://jank-lang.org/blog/
Thanks for taking the time to comment!
- mtlmtlmtlmtl 3y agoWell, in that case, if you have any issues that are somehow well suited for a reasonably experienced C/Lisp programmer with almost no C++ experience(unless shaking my head over the code in the Arduino stdlib counts...), then maybe I'll sit down with one of those!
- Jeaye 3y agoThere will be a lot of room for this, once I build out more of the features. In particular, there will be a lot of Clojure libraries which need to gain jank support. Clojure doesn't require "porting", so to speak, since it has a special .cljc file which can use reader conditionals to check the host that it's in (clj, cljs, cljr, jank, etc). So anywhere those libs are using Java interop, we'd need to wrap it to use native interop instead. On the compiler and tooling itself, I have some open issues here: https://github.com/jank-lang/jank/issues https://github.com/jank-lang/jank/issues The vast majority of it is heavy C++ work, though. Outside of that, the biggest gains will come from time spent on packaging, distribution, and testing on various platforms. And if none of that sounds interesting or applicable, don't worry. Just be sure to join the Slack channel and hang out with us. :)