Hacker News Reader

Comment by mardifoufs | Hacker News Reader

I think the LuaJIT maintainers have some issues with recent additions to the language, and with the direction that the Lua team has taken. So yes, frozen to 5.1 for the foreseeable future except for some features from more recent versions.

View on HN

I can't seem to find any information about this. What issues did LuaJIT maintainers have with upstream Lua?

https://github.com/LuaJIT/LuaJIT/issues/929

> the real issues of the language

> irrelevant or not-well-thought-out features

Looking for specific examples of these. The scoped finalization construct cited in a sibling comments is a great example of this. Are there more?

The issue linked in the sibling comment is the main one, but for a specific example of them having reservations about a feature in a more recent version, there's this:

https://github.com/LuaJIT/LuaJIT/issues/1013#issuecomment-16...

That's an awesome example, thank you. I'm making my own language and it's hard to overstate how thorny the evaluator and call stack code can get once seemingly neat features are added. I'll try to avoid making the same mistakes. I agree with him that implicit scopes for resource management serve no purpose in a dynamic language.

Oh wow, from Mike Pall himself (I know he "retired" from the maintainer position but glad he is still providing guidance (and then some id imagine))

Seeing a project and a community functioning like this is simply inspiring.

Reply on news.ycombinator.com