jank is a programming language that asks a question most language designers avoid: what if you took Clojure's immutable-data, REPL-driven philosophy and bolted it directly onto the C++ type system, with no FFI layer, no marshalling, no ceremony? The answer, if jank delivers, is a tool that lets you write idiomatic Lisp until you need raw performance, then drop into C++ inline without leaving your editor or your mental model. The interop story is the headline feature and it's aggressive. You :include C++ headers, call templates, catch Boost exceptions, cast to std::string, and use RAII — all from Clojure syntax. The filesystem example on the homepage isn't a toy: it calls boost::filesystem::filesize, catches a typed C++ exception, and returns a Clojure map. That's real interop, not a thin wrapper around extern "C" functions. The ImGui/GLFW game-dev example goes further, calling OpenGL context setup, ImGui widget functions, and a render loop from what looks like ordinary Clojure. jank uses a Clang-based JIT compiler under the hood, which means it compiles Clojure to C++ and then JIT-compiles that C++ via LLVM. This is architecturally unusual — most JIT languages target their own bytecode or LLVM IR directly. Going through C++ as an intermediate representation means jank inherits Clang's entire optimization pipeline and, critically, its ability to parse real C++ headers. That's what makes the interop possible without code generation or binding tools. The project management layer uses Leiningen, Clojure's traditional build tool, extended with a native dependency system that can find installed C/C++ libraries or build them from source. The project.clj for the ImGui demo pulls in imgui-glfw-sys and imgui-opengl2-sys packages with optimization profiles for debug and release builds. This is the kind of infrastructure work that signals a project thinking about real adoption, not just a proof of concept. The risk profile here is substantial. jank is attempting to be simultaneously a faithful Clojure dialect (with reader conditionals, nREPL support, and idiomatic data structures) and a first-class C++ citizen. Those two worlds have deeply different assumptions about memory, types, and control flow. Immutable persistent data structures and RAII are not natural friends. The fact that jank appears to make this work — at least in the demos shown — is genuinely impressive, but the demos are carefully chosen showcases, not stress tests. The game-dev angle is smart positioning. Game developers are one of the few audiences that simultaneously want rapid iteration (REPL-driven development), functional data patterns (game state management), and zero-compromise native performance (render loops, physics). Unity's C# and Godot's GDScript both make tradeoffs here that jank could potentially avoid. Whether the community materializes around this pitch is the real question — languages live or die on ecosystem, not features. What jank is not, at least yet, is battle-tested. The version numbers (2026.06-x) suggest very early releases. There's no mention of production deployments, benchmarks against equivalent C++ code, or the size of the contributor base. The technical ambition is real, but the distance between a compelling demo and a language you'd ship production software in is measured in years and thousands of users finding the edges.
