3 ms·
Thanks for pointing that out. I was going to ask why it appears to have stalled a year ago, but I guess the author got distracted by something shiny: https://g
by justinmk 12y ago
Thanks for pointing that out. I was going to ask why it appears to have stalled a year ago, but I guess the author got distracted by something shiny:
https://github.com/richardhundt/shine https://github.com/richardhundt/shine
Shine appears to address a similar need as the luv "ray" branch, _without_ libuv, with a modified version of LuaJIT[1]. I wonder if the author plans to patch LuaJIT upstream?
A recent HN discussion[2] left me wondering where to look for a high-quality well-maintained lua "stdlib". luvit appears to be an entire distribution with its own package manager instead of luarocks/moonrocks. I'm now looking at luv and luajit-libuv. shine looks like a very interesting alternative, but the modified LuaJIT makes it problematic for deploying to users who want to use system-provided LuaJIT.
[1] https://github.com/richardhundt/shine#introduction https://github.com/richardhundt/shine#introduction
[2] https://news.ycombinator.com/item?id=8191345 https://news.ycombinator.com/item?id=8191345
- srean 12y agoI might be remembering it wrong, but iirc it so transpired that there was a thread on the Lua mailing list about the unfortunate clash in the name 'luv'. richardhundt/luv is older of the two pieces of software but Richard graciously offered to yield (pun intended) the name to luvit folks and continued to develop on his code and ideas under a new name, shine. richardhundt/luv is more than an obvious wrapper over libuv whcih is what luvit/luv intended to be. Please bear in mind I might have got the exact events (Gawd, pun again, this time unintended) wrong, but if you are interested you will be able to find this on the lua mailing list archives.
- justinmk 12y agoThanks very much.