user237

I've been paying attention to this project for a while since the space for Lua frameworks is rather quite small. While I am interested in evaluating it once it matures, the biggest stumbling block for it so far is that the documentation and tutorials needs more polish and love.

I understand that it may be difficult finding someone willing to edit and clean up documentation, much less fill it in where things are currently empty, but it's not too soon to try and prioritize this. It may be worth trying to collect donations to start a bounty in the hopes of attracting someone who wishes to do the work and I personally would be happy to pitch in what I could toward it.

I've really enjoyed poking at OpenResty and I found Lapis to be the most mature framework working with it.

However, I find the use of Moonscript for its examples sites and the obvious preference for it in the documentation to be quite maddening. Using moonc to compile things down to Lua doesn't really make tracing through code any better when trying to gain a full understanding of the stack.

I've got very little desire to go out of my way to learn Moonscript since I will not get company approval to work in it and I cannot train my coworkers on it just so they can learn to use Lapis. Already it was a stretch adopting Lua where I am and to be quite honest, I really haven't liked what I saw of Moonscript anyway. I don't want or need classes and its associated machinery, I particularly do not want semantic whitespace.

I really hope to see more focus placed on making Lua proper a first-class citizen for the framework, including provided examples. Otherwise, Lapis does look like the right tool for the job and I liked many of the other decisions made over it.