4 ms·
I strongly second that. We are more and more former users of LuaJIT who either don't use LuaJIT anymore, or think it is not a good long-term solution, because o
by catwell 8y ago
I strongly second that. We are more and more former users of LuaJIT who either don't use LuaJIT anymore, or think it is not a good long-term solution, because of those two issues (and absence of support of recent Lua versions).
In addition to that, people working on Titan say it could become an alternative to C for people who write applications in PUC Lua + C:
- It has an FFI so it can be used to implement bindings.
- It can also be used to extract performance-sensitive code from Lua into a compiled language.
- It should support newer Lua versions, being developed by people from PUC / close to PUC. Yay, 64 bit integers and bitwise operators!
- hugomg 8y agoYup, this is the idea. :) If you don't mind, I'm curious about what applications you currently use Lua for.
- jdright 8y agoThis will be very useful for platforms (mostly game consoles) where JIT are prohibited / security risk.
- catwell 8y agoAt work, I use Lua 5.3 embedded into a large-ish (a few hundred thousand LOC) cross-platform (runs on Windows, Mac, Linux, iOS, Android) C application as a way to extend it. We have bindings for a lot of the C functions and use Lua for prototyping. We keep the code in Lua in production if possible, or rewrite in C if performance issues force us to. Personally, I use Lua for a lot of other things including Web development.