Strategy Game Collaboration

Experimental RTS/Space sim Collaborative Coding Project.
The goal is to design a game with structure/settings/balance of Starcraft and scale of Eve Online(i.e. huge space battles, space empires,etc).
Though this wouldn't stop anyone from contributing code/feedback/criticism, i'll be coordinating the project.
All code/ideas should be posted in this and subsequent threads which i'll start as needed.
step #1: We will collaboratively create a name for our project.
Each suggestion must explain why this name fits the project and why its better then any other generic name.

>>378
Except Lisp and Factor are not interepted unless you want them to be. The code is loaded into memory and executes straight away, there's no JIT involved ( you can do something like JIT for scripting, if you want to, if you include the entire LISP implementation (somewhat large - 5-20MB), you could compile code at runtime, and run it right away. ). It's not memory hungry unless you make it memory hungry:
1)You want code which allocs(conses) less? Sure, you can do that. If you're so hung up about memory usage, you could make entirely cons-less code, but don't forget that modern games are very resource hungry, much more than any Lisp implementation is.
2)You want a small executable: tree shake the image, and you can get it very small, some people have gotten small tools to be under 50-100KB. This is usually done only for deployment, it's slightly less work to just distribute compiled packages as FASL's.

but it will be obviously slower
How many times was it mentioned that functions are compiled to native code? It will be slower than C, unless you plan on optimizing everything, but this speed loss is not important except on time sensitive code, which can be optimized or even written in C if needed.
and require runtime to be installed
What runtime? Your game will need to include dll's/libraries anyway, for sound/graphics/movies/compression/... Runtimes are not installed in the user's system, they're just bundled files along with everything else. You could of course pack everything up in one executable which runs out of the box, but why do such a thing?

>compared to native code
This is already natively compiled, the only addional cost is manually loading code into memory, as opposed to the OS doing it for you. Do you know that using an executable packer such as UPX on your code, would make it manually load the code into memory? It's no greater cost than that.