Re: LuaJIT project governance
- From: Alex Szpakowski <aszpakowski@xxxxxxxxx>
- To: luajit@xxxxxxxxxxxxx
- Date: Tue, 18 Aug 2015 15:16:36 -0300
On Aug 18, 2015, at 2:05 PM, William Adams <william_a_adams@xxxxxxxxxxx>
Also, along the lines of 'vision', I say ditch the 'drop-in' compatibility
with Lua 5.1. We all know it's not a straight drop in replacement, so we
should just move on from that stance, as it will probably relax some of the
constraints that are currently in the system. Either that, or make a
concerted effort to remerge this work back to Lua mainline, and end the
differences. My vote would be for the former.
Do you have specific practical examples of where this would be a large benefit
to LuaJIT as a whole (its ecosystem and APIs, not just its codebase)? Maybe
motivated people could create a fork to evaluate what that sort of change in
direction could do in terms of code.
Keep in mind LuaJIT’s ecosystem is fairly dependent on PUC Lua’s right now,
including decades of various documentation and existing Lua code. What would
entice me to use versions of LuaJIT which might throw that away? What type of
people and projects do you have in mind who will use LuaJIT in the future?
Other related posts: