3 ms·

I like Luvit, but what makes node so awesome is people wrote evented drivers for databases and such. I'm not sure that there is a community there to do that aga

I like Luvit, but what makes node so awesome is people wrote evented drivers for databases and such. I'm not sure that there is a community there to do that again in Lua. Also, the openresty approach seems like an interesting way to get high performance web lua without writing evented code.

pygy_ 14y ago
I believe that both Luvit and OpenRESTy use coroutines to manage async code. You're not forced to use callbacks as you are in JavaScript.
kansface 14y ago
Lua is an embedded language. I don't ever see the day when Luvit will be used for a backend server in lieu of Nodejs. In general, you shouldn't ever need an evented DB driver except for perhaps sqlite.
- gruseom 14y ago
  That Lua is an "embedded" language is a strength, not a weakness: it's small enough and interoperable enough to be used in ways that most language implementations can't. The fact that it can do this while at the same time being quite a bit more powerful (and efficient) than Javascript is a marvel of design. It has yet to be fully appreciated. We're going to see a lot more Lua on the server.
- mburns 14y ago
  Isn' that a little like saying: "Javascript is an embedded language. I don't ever see the day when node.js will be used for a backend server in lieu of php/perl/python/ruby."
- hermanhermitage 14y ago
  Kansface, the main pros for lua(jit) are reduced memory footprint and generally superior code execution performance to js. There's also the FFI which is more sophisticated in lua(jit) than node. So depending on the details, I think there is a strong argument for luvit over nodejs - particularly when the breadth of the nodejs ecosystem isn't required and when a stronger language implementation is required.
  - finnw 14y ago
    Another pro for Lua is it has weak references and JS does not.
philips 14y ago
We are using Luvit to build a monitoring agent using an async programming model. Using node was not an option given the memory consumption. https://github.com/racker/virgo https://github.com/racker/virgo That said there are some modules coming out of the community: https://github.com/luvit/luvit/wiki/Projects https://github.com/luvit/luvit/wiki/Projects
- Ecio78 14y ago
  These links are broken: https://github.com/twojcik/luvit-redis https://github.com/twojcik/luvit-redis https://github.com/yields/rounded https://github.com/yields/rounded

pygy_ 14y ago

I believe that both Luvit and OpenRESTy use coroutines to manage async code. You're not forced to use callbacks as you are in JavaScript.

kansface 14y ago

Lua is an embedded language. I don't ever see the day when Luvit will be used for a backend server in lieu of Nodejs. In general, you shouldn't ever need an evented DB driver except for perhaps sqlite.

gruseom 14y ago
That Lua is an "embedded" language is a strength, not a weakness: it's small enough and interoperable enough to be used in ways that most language implementations can't. The fact that it can do this while at the same time being quite a bit more powerful (and efficient) than Javascript is a marvel of design. It has yet to be fully appreciated. We're going to see a lot more Lua on the server.
mburns 14y ago
Isn' that a little like saying: "Javascript is an embedded language. I don't ever see the day when node.js will be used for a backend server in lieu of php/perl/python/ruby."
hermanhermitage 14y ago
Kansface, the main pros for lua(jit) are reduced memory footprint and generally superior code execution performance to js. There's also the FFI which is more sophisticated in lua(jit) than node. So depending on the details, I think there is a strong argument for luvit over nodejs - particularly when the breadth of the nodejs ecosystem isn't required and when a stronger language implementation is required.
- finnw 14y ago
  Another pro for Lua is it has weak references and JS does not.

philips 14y ago

We are using Luvit to build a monitoring agent using an async programming model. Using node was not an option given the memory consumption. https://github.com/racker/virgo https://github.com/racker/virgo That said there are some modules coming out of the community: https://github.com/luvit/luvit/wiki/Projects https://github.com/luvit/luvit/wiki/Projects

Ecio78 14y ago
These links are broken: https://github.com/twojcik/luvit-redis https://github.com/twojcik/luvit-redis https://github.com/yields/rounded https://github.com/yields/rounded