Julia vs Lua

Julia runs almost as fast as (and in fact in some cases faster than) C code.

Dynamic and high level, but does not isolate the user from properly thinking about types. Can do explicit type signatures which is great for teaching structured thinking.

Out of the box Julia has a very good Read-Eval-Print-Loop, which both completes functions and types, as well as completion based on history of previous statements. It integrates well with the shell and has an excellent online help system.

Julia code is easy to read and avoid a lot of unnecessary special symbols and fluff. It uses newline to end statements and "end" to end blocks so there is no need for lots of semicolons and curly braces. It is regular in that unless it is a variable assignment, function name always comes first. No need to be confused about whether something is a method on an object or a free function.

Unlike Python and Ruby, since you can annotate the types a function operates on, you can overload function names, so that you can use the same function name for many data types. So you can keep simple descriptive function names and not have to invent artificial function names to separate them from the type they operate on.

The Julia language is written in itself to a much larger extent than most other languages, so a budding programmer can read through the depths of the standard library and learn exactly how things work all the way down to the low-level bit-twiddling details, which can be englightening.

Julia has built in n-dimensional arrays similar in functionality as Python's numpy.

You can have multiple functions with the same name, but doing different things depending on function arguments and argument types.

Julia requires no boilerplate code – a beginner needs to write only the parts they care about. This combined with the REPL provides the best learning experience available.

Julia provides a high level of abstraction, making platform-independent programming trivial and easing the learning curve.

You can perform operations on scalars, for example 2^2 or [1, 2, 3].^2.

Julia allows you to edit Julia code in the language itself and write powerful macros. It is a great introduction to metaprogramming features

The Julia REPL allows quickly testing how some code behaves and gives access to documentation and package management immediately in the REPL.

One of the best features of Lua is its very well designed C API. This is very useful if you have an existing C library you need to integrate with Lua or quickly get a Lua script running on the C side of the game.

Finally Lua plays so nice with C that if you need to optimise for speed you can re-write it in C a lot easier than other languages.

The official Lua documentation is very helpful and thorough. There are also a large number of online resources or books with lots of helpful information for beginners and advanced users alike.

Lua can be built on any platform with a ANSI C compiler.

Other than that, Lua is extremely small. For example, the tarball for Lua 5.2.1 is only 245K compressed and 960K uncompressed (including documentation).

When built on Linux, the Lua interpreter built with the standard libraries takes 182K and the Lua library takes 243K.

The small size and the ability to build with a C compiler make Lua an extremely portable language that can run on a lot of different systems and computers.

Easy to learn.

Lua's performance compares very well to other languages, If performance needs to be further improved you can:

1. Implement critical parts in C
2. Use the LuaJIT compiler. The LuaJIT compiler is a drop in replacement for the stock compiler and provides significant performance improvements. From the overview page:

LuaJIT speeds can rival code written in C.

Many different game engines (e.g. Elder Scrolls series, ToME) use Lua for scripting, and it's runtime is designed for embedded use.

The Lua syntax is modeled from Modula, a language known for being a fantastic introduction to programming.

The Lua syntax also has the following key characteristics:

• Semicolon as a statement separator is optional (mostly used to resolve ambiguous cases as in a = f; (g).x(a)).
• Syntactic sugar for function calls (f'string', f"string", f[[string]], and f{table}) and method calls (obj:m()).

Due to the growing popularity, Lua has a rather large and helpful community surrounding it.