Viewing profile — Jeaye

Protocols, records, and the like will be implemented in jank. They haven't been prioritized for two reasons. Firstly, historically, jank had a closed object model for performance, …

I am the creator of jank. I am also not interested in a flame war. The key differentiator for jank is the seamless C++ interop, which is a problem not many people are willing to ta…

Yes! This is exciting to see. Erin Catto is such a cool hacker. Thank you, Erin, for sharing your code with the open source community. There wasn't anything about determinism in th…

I am researching for a talk on the philosophy of code, the similarities of engineering and art, and why we enjoy reading old code. This amazing work you folks have done may be an i…

There are three aspects of this which concern me the most: personal, open source, and business. On the personal side, code is art , not a means to an end. Many of us love coding. F…

Babashka's interop is with Java, since Babashka uses a Graal-compiled version of the JVM. It's still the JVM, just baked down. This is different from interop with the native world.…

I am developing a test suite for portability of clojure.core across dialects. You can find it here: https://github.com/jank-lang/clojure-test-suite Currently, we have Clojure, Cloj…

Once you learn Clojure's syntax and semantics, you're no longer bound to the JVM. There's ClojureScript (JS), ClojureCLR, ClojureDart, jank (C++), Basilisp (Python), babashka (SCI)…

jank's custom IR is completely separate and unrelated to LLVM IR, aside from both of them being SSA-based IRs. We go from jank's AST into jank's IR into C++, which we then give to …

As another said, jank is not replacing LLVM or LLVM IR. We still use LLVM IR! There is a diagram here which shows the pipeline: https://book.jank-lang.org/dev/ir.html The main thin…

The first three paragraphs here are on point! jank's IR passes will not worry much about things like load/store optimization, register allocation, inlining C++ functions, etc. Thes…

I spoke with a couple Clang and LLVM devs about MLIR when I was doing the original design for jank's IR. The general consensus was that MLIR added a great deal of complexity on top…

Hey lemming! You're right, which is why it should be used sparingly. Since clojure.core is compiled (on the JVM) with direct linking, reacting to var changes isn't an intended conc…

I think they mean the video thumbnail, which may or may not be AI-generated.

I'm working on the jank programming language! https://github.com/jank-lang/jank It's a native Clojure dialect which is also a C++ dialect, including a JIT compiler and nREPL server…

As much as any C++ project would, yes. That includes either through the C ABI or through the various C++/Rust interop mechanisms.

jank is Clojure and will track upstream Clojure development. I'm working closely with the Clojure team and other dialect devs to ensure this remains the case. I am leading a cross-…

JIT compiling C++ is definitely the slowest thing we do. However, we're working on two different codegen modes. 1. C++ 2. LLVM IR The IR is much faster to compile, but its perf isn…

Carp is great and I would love to include a mode of jank which is very much Carp-esque. If you're interested in working together on this, please let me know.

We have a working nREPL server, but it's not yet merged into the jank repo. https://github.com/kylc/try-jank There's a Clang bug getting in the way of the progress we want, so we'l…