The JVM would like to have a word with you.

LuaJIT would like to have a word with JVM.

Plus, Lua isn't controlled by a creepy asshole who thinks the NSA is essential and says stupid shit like "Who's ever heard of government misusing information?"

I'm curious. I persume, with quite powerful hardware, task's not going to be trivial and may require some concurrently running processes.

JVM has threads. Akka adds actors (those seem quite nice when used with Scala). Does Lua/LuaJIT offer something simple-looking-yet-powerful in that area?

This comment is a bit incoherent, so I'm not sure if I'm responding correctly at all. Your C/C++ program can contain any number of Lua states, and can also contain an infrastructure for passing messages between these states. The states themselves are single-threaded. Within a single Lua state, you can have any number of coroutines, but these do not work like JVM threads or goroutines; they must be scheduled explicitly.

I'll wait an hour for it to warm up, then come back and hear what it has to say.

Nitpicking: while JVM implementations can run, they're not particularly tailored for dynamically typed languages.

Clojure would like a word with you.

Just because you can build a dynamic language on a vm doesn't mean it was designed and optimized for it.

I don't think invokedynamic beats V8.

Source?