If you can continue to maintain the logic of Lua, then Lua can directly serve as the backend, such as Luvit. . I haven't used it, so I don't know if it's good or bad. Of course, since lz is based on nodejs, most of the time it can’t be put down to support lua, which is a bit painful. I really don’t know if there is such thing as nodejs lua binding. Otherwise, it is not very troublesome to write one by yourself. Nodejs is extended and then called lua. It is not difficult to implement this layer of wrapper in native. It is just a workload and the efficiency should be better than js implementation. The lua interpreter is better.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Well, I implemented a simple synchronous lua binding for nodejs myself.
If you can continue to maintain the logic of Lua, then Lua can directly serve as the backend, such as Luvit. . I haven't used it, so I don't know if it's good or bad. Of course, since lz is based on nodejs, most of the time it can’t be put down to support lua, which is a bit painful. I really don’t know if there is such thing as nodejs lua binding. Otherwise, it is not very troublesome to write one by yourself. Nodejs is extended and then called lua. It is not difficult to implement this layer of wrapper in native. It is just a workload and the efficiency should be better than js implementation. The lua interpreter is better.
Make good use of search: https://www.google.com/?gws_rd=ssl#newwindow=1&safe=off&q=js+l...
nodejs calls the command line and executes lua