The Lua community needs to learn to move on
4 hours ago
- Mike Pall's deletion of old LuaJIT tags reflects the challenge of getting users to upgrade, aiming to force upgrades after decades of outdated versions.
- The Lua community struggles with supporting multiple old language versions (5.1–5.5 and LuaJIT variants), leading to a paralyzing maintenance burden.
- For Lua as an extensible language, the author argues for moving to support only the latest PUC-Rio Lua and LuaJIT, similar to other dynamic languages.
- The historical Lua/LuaJIT schism and the author's own compat-5.3 library contributed to a 5.1 anchor that persists today.
- Teal, a typed language compiling to Lua, aims to bridge version gaps by generating code for targets 5.1 to 5.5.
- Library authors should follow the leads of Roberto Ierusalimschy and Mike Pall by EOLing old versions, rather than indefinitely supporting legacy ecosystems.