4 ms·
At the time I'm writing this, the latest commit in https://github.com/LuaJIT/LuaJIT https://github.com/LuaJIT/LuaJIT was 26 minutes ago. There has also been a c
by tom_mellior 7y ago
At the time I'm writing this, the latest commit in https://github.com/LuaJIT/LuaJIT https://github.com/LuaJIT/LuaJIT was 26 minutes ago. There has also been a constant stream of commits over the last months (I didn't check further), but no frantic activity. Almost all commits in the moonjit history also seem to be be cherry-picks of these LuaJIT commits.
So calling LuaJIT unmaintained, and saying that moonjit "continues development" both seem a bit exaggerated to me.
- cwyers 7y agoThe last release was a beta from May 2017.
- fsfod 7y agoThe last time Mike Paul pushed anything is almost a year ago until two weeks ago based on the two RSS feeds I use. The Git commit dates could be unreliable from either cherry-pick shenanigans or him just not bothering to push the changes until two weeks ago.
- acqq 7y agoMaybe compare your feeds with: https://github.com/LuaJIT/LuaJIT/commits/v2.1 https://github.com/LuaJIT/LuaJIT/commits/v2.1 I see quite regular commits there?
- siddhesh 7y agoThe v2.1 branch of moonjit specifically aims to remain "luajit-like" in the sense that it is the explicit goal to make sure we don't add incompatible features and we definitely don't make it so that if Mike Pall decides to continue development after a year (which he appears to have done, although one can never be sure given his record over the past few years), we can easily enough merge patches. The master branch is where moonjit development is more active with people adding 5.2 and 5.3 features and new architectures too. It is in a way a different direction from luajit (since Mike specifically stated that he intends to remain incompatible with stock Lua because his dialect is better) and hence may not necessary converge with luajit if it ever actually comes back to life.