3 ms·
From observing what has happened to Lua 5.1.5, LuaJIT, Lua 5.x.x>5.1.5, Python 2, and Python 3, it appears to me (with my limited experience in software develop
by andrewmcwatters 9y ago
From observing what has happened to Lua 5.1.5, LuaJIT, Lua 5.x.x>5.1.5, Python 2, and Python 3, it appears to me (with my limited experience in software development) that languages grow to mature to a peak where they provide their most value and productivity into languages which don't stop growing. These languages eventually prune productivity gains due to API breakage and library severance across major versions, to the point where their ecosystems become disparate.
I'm not sure I see the benefits of using anything beyond Lua 5.1.5/LuaJIT these days in game development. I'm not sure what the status of version adoption is beyond this particular field, but I contribute and participate in open source Lua-based game development projects to such an extent that I see the same names over and over again and have these people on my friends lists across different platforms.
A lot of these folks are all also still using LuaJIT, which has kept much of the community from moving forward, because if you're _not_ using it, you're missing out on some significant performance gains which are very relevant in gamedev.
- sitkack 9y agoLuaJIT is indeed a big draw, but it also has a bunch of 5.2 features, esp goto. 5.3 brought integers which is awesome because 64 bit datatypes can round trip through Lua will full fidelity.