News for hackers. Stuff that matters.
Re:Compiling to Lua by nilved on Friday August 23, 2013 @08:18PM (#6266988)
I hope that Luvit[0] is what will bring Lua to the forefront of web development. It has such remarkable potential. It could completely (and should completely) replace node.

[0] http://luvit.io

Re:Compiling to Lua by cmwelsh on Friday August 23, 2013 @09:05PM (#6267126)
It seems like a step backward. Dealing with callbacks manually is an unnecessary hassle compared to being able to use "green threads". See python gevent and ngx_lua for examples of people doing things this way.
Re:Compiling to Lua by someone13 on Friday August 23, 2013 @09:36PM (#6267200)
Check out Luv - an attempt to use Lua's coroutines to do green threads/fibers, integrated with libuv.

https://github.com/richardhundt/luv

Re:Compiling to Lua by kodablah on Saturday August 24, 2013 @12:44AM (#6267658)
luv does a fantastic job of sticking with Lua coroutines. The master branch still has zeromq in it, but the latest work is done in the ray branch. Sadly, it doesn't seem the project is moving, so most of the libuv features are not yet implemented the "ray" way.

Edit: Seems ray does have most of libuv features, sorry.

Re:Compiling to Lua by chubot on Friday August 23, 2013 @11:05PM (#6267424)
Yeah I never really understood luvit. Callbacks make sense in JavaScript because it doesn't have coroutines. But Lua has coroutines! So why does luvit use callbacks? It does seem like a step backward.
Re:Compiling to Lua by ufo on Friday August 23, 2013 @11:49PM (#6267534)
Historical reasons. The guy who wrote luvit knew NodeJS but didnt know Lua when he started working on it.
Re:Compiling to Lua by anonymoushn on Friday August 23, 2013 @10:56PM (#6267399)
and node-fibers :o