jank VS DOOM-3

There's an effort afoot to bring this to the Clojure world, with the lovely name jank: https://jank-lang.org

I also liked that reference since I had not heard of Jank before. It is a work in progress so I just added a calendar entry for 9 months from now to check it out. https://jank-lang.org/

There 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

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. :)

On the top of using C++ for scripting, and related to the discussion of CERN's ROOT/Cling, I am developing a Clojure dialect on C++/LLVM called jank: https://jank-lang.org/

jank is a true Clojure, meaning you get interactive, REPL-based development and a whole stdlib of persistent, immutable data structures and functions to transform them. But it's also C++, so you can write inline C++ within your jank source, and interpolate jank values within that. You can link with existing native code using LLVM and you can embed jank into your existing native projects to use for scripting.

jank is pre-alpha, right now, and I've only been showing it to Clojure devs so far, but there's a huge audience of C++ devs which may be interested in introducing Clojure to their native code.

jank (https://jank-lang.org/) is a Clojure dialect on LLVM with C++ interop. In this talk, Jeaye will cover jank's use cases, some challenges around building a native Clojure dialect, and some insights about Clojure itself found only by spelunking deep into the Clojure compiler.

I wonder if Jank [1] could be such a Lisp? I haven't played around with it, but I really like the idea and would love to see it get more traction.

[1]: https://jank-lang.org/

This isn't usable yet, but in active development by the author, and looks promising: https://jank-lang.org/

Jank looks pretty legit: https://jank-lang.org/

>As an aside, I find the idea of writing game code in unmanaged C++ perplexing.

https://github.com/id-Software/DOOM-3

I don't know of a Carmack engine that doesn't have a benchmark facility.

timedemo uscache

The DOOM3 source is here https://github.com/id-Software/DOOM-3

There are lots of fascilities for recording and playing back demos. The author could record their own gameplay and play it back in realtime vs running timedemo (which plays back as fast as possible).

    2865: cmdSystem->AddCommand( "recordDemo", Session_RecordDemo_f, CMD_FL_SYSTEM, "records a demo" );

The probability a company uses visual scripting seems to correlate to how much they embrace parsing and reflection. Whenever someone is skeptical about the value of those things I just remind them that Doom3 has a C++ parser and reflection generator in it's original non-BFG release.

No but there are open-source engine ports, you only need the content packs (wad) to play it with those. Doom 3 is open source tho, they violated some licenses or something and released the source a couple of years ago (https://github.com/id-Software/DOOM-3)

Not familiar with other platforms but the Windows version uses DirectInput8 polling to retrieve keyboard and mouse state, as seen here.