Show HN: LadyLua, batteries-included static Lua 5.1 interpreter

Nice effort, my main question is why not the &quot;standard&quot; go lua wrapper, golua[1]? More specifically, why implement a lua interpreter in go, when there is a perfectly useable c-api wrapper for go?<p>[1] <a href="https:&#x2F;&#x2F;pkg.go.dev&#x2F;github.com&#x2F;aarzilli&#x2F;golua&#x2F;lua" rel="nofollow">https:&#x2F;&#x2F;pkg.go.dev&#x2F;github.com&#x2F;aarzilli&#x2F;golua&#x2F;lua</a>

This is really cool!<p>Why Lua 5.1 and not 5.2 or 5.3? What does the marshalling story between Lua and the builtin Go modules look like? What would it take to add more builtins or richer marshalling?<p>I love seeing other Lua implementations.

Go seems like a suboptimal language for implementing an interpreter, since it lacks the low level primitives to make a fast interpreter loop.<p>But I guess, as will all things Go, that it will be fast enough for a good amount of use cases, and having a language native dependency rather than messing with C libraries is always a plus.

I think the readme could use some examples of where this might be useful

This doesn&#x27;t appear to really do anything to address the one big problem I&#x27;ve had with using Lua for larger applications. Does GopherLua still have global-by-default variables?

It&#x27;s a real shame to pin to Lua 5.1 but not use LuaJIT.