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.

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.

> 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?