I love Lua and code in it almost every day for fun, but yeah I'm pretty sure LuaJIT is just "done" now?
I love Lua and code in it almost every day for fun, but yeah I'm pretty sure LuaJIT is just "done" now?
The newer versions of Lua basically implemented features that LuaJit already had or that would mean a performance trade off. I am still using Lua 5.1 (which is from 2012) because there is no reason to upgrade.
If you design something well, you don't need to push new features every year. Stability is underrated.
I'm not sure that's true. Maybe LuaJIT was never going to add the features it's missing from Lua 5.2, 5.3 and 5.4. However, when Mike Pall stepped back in 2015 [0], he had still been planning to further improve the implementation - for example with a new garbage collector [1] and "hyperblock scheduling" [2] (which remain unimplemented), plus 64-bit pointer support (which was eventually completed by other people).
[0] https://www.freelists.org/post/luajit/Looking-for-new-LuaJIT...
I am wondering what is Mike Pall working on now.
They also believe all software, no matter how relatively small or simple, has bugs.
It is absolutely baffling. Job security fears I guess. There are so many incompetent software developers. These beliefs protect them from having to face their incomeptence.
That, and most package repository browsers have statistics and people are racing. How many times has it been downloaded? How many projects use it? How many stars did it get?
The more one liners you submit as a package, the better, it seems, as well.
E.g. closures are not yet supported by the JIT; notwithstanding this, it is a great and still very useful technology.
It has a few extras but they agree with the original luajit authors opinion that not every 5.2 feature can be made in jit.
I had high hopes for moonjit, but development on it has ceased. There are other forks—openresty and raptorjit come to mind—but they don't have feature parity.