01:37:00  * DarkGodquit (Ping timeout: 240 seconds)
02:07:49  * a__96joined
05:14:24  * dan336joined
05:39:20  * SkyRocknRolljoined
06:04:08  * dan336quit (Quit: Leaving.)
07:15:16  * SkyRocknRollquit (Ping timeout: 255 seconds)
07:32:56  * SkyRocknRolljoined
08:10:31  * DarkGodjoined
12:10:24  * SkyRocknRollquit (Ping timeout: 264 seconds)
13:18:50  <rphillips>good morning
14:27:46  * dan336joined
14:34:14  * DarkGodquit (Ping timeout: 244 seconds)
14:34:42  * DarkGodjoined
14:37:55  * SkyRocknRolljoined
14:51:06  <creationix>morning
14:51:12  <rphillips>wb :)
14:51:23  <rphillips>how was the presentation?
14:51:53  <creationix>not bad, though only 3 people showed
14:51:59  <creationix>about 11 RSVPed
14:52:18  <creationix>I think next time, we'll need to prefix it with a short presentation on lua the language
14:52:30  <creationix>that helps more than history or design of luvit I think
16:48:28  <kostco>i wonder how luvit would compare to this
16:48:28  <kostco>http://www.ureq.solusipse.net/
17:48:15  * SkyRocknRollquit (Remote host closed the connection)
18:12:23  <creationix>kostco, could you link to your docs again please?
18:17:42  <kostco>creationix: https://github.com/kaustavha/luvit-docs
18:18:10  * travis-cijoined
18:18:11  <travis-ci>luvit/luvit#2562 (master - 8b27bec : Tim Caswell): The build passed.
18:18:11  <travis-ci>Change view : https://github.com/luvit/luvit/compare/befeb7aa7260...8b27bec825a6
18:18:11  <travis-ci>Build details : https://travis-ci.org/luvit/luvit/builds/84971018
18:18:11  * travis-cipart
18:25:29  <creationix>kostco, nice work on the docs
18:25:49  <kostco>thanks! :)
18:26:03  <kostco>still a lot to do, but its a start
18:26:25  <creationix>I wonder why we have the "los" module
18:26:32  <creationix>jit.os gives that info already
18:26:55  <creationix>and helpful should probably be moved to lit as a third-party module
18:27:08  <creationix>the docs give good visibility to what's inside luvit
18:27:21  <kostco>yep, bird eye view
18:28:12  <kostco>i think los makes sense, or perhaps somehow wrap things and export as os like node. jit.os is something most people would find a little strange after working with an api that reads like node
18:29:21  <kostco>i wonder if itd be possible to add other things in helpful and extend the standard lua string and table definitions with things that are required often. perhaps only extend them if the user requires helpful somewhere. (not sure how/if that would work though)
18:32:59  <kostco>can we/do we want to move luvit-docs into the luvit org for more visibility?
18:46:46  <creationix>sure, we can move it
19:05:57  <rphillips>creationix: there use to be an 'os' module
19:06:06  <rphillips>which was different than the os module from lua
20:00:37  <kostco>oh yeah didnt know there was a lua os module
20:02:00  <kostco>im not in the luvit org, can you add me / move in the luvit-docs?
20:02:35  <kostco>perhaps down the line itd make sense to just add more features and extend luas os and document that instead of having los. node has a few more useful things
20:54:08  <creationix>kostco, luvit 1.x just extended (or replaced, I don't remember) the existing lua "os" module.
20:54:33  <creationix>I think I'm find with extending as long as it doesn't change any existing behavior in the lua built-in
21:01:36  <creationix>kostco, ok, send invite to luvit team on github
21:01:40  <creationix>*sent
21:20:52  * Michalikquit (Ping timeout: 256 seconds)
22:25:45  * Michalikjoined
23:06:40  * rweichlerjoined
23:06:53  <rweichler>does anyone know of any projects that currently use this that i could look at?
23:15:05  <rweichler>trying to decide between using this and go, since lua is in my frontend
23:40:51  <dan336>rweichler: what sort of project are you looking for?
23:42:03  * DarkGodquit (Quit: Leaving)
23:44:20  <kostco>rweichler: it really depends a lot on your project. This monitoring agent is written in it since its easy to write things with it, and luajit gives us nice runtimes/memory overhead/total space on disk etc so we're not taking too much away from customers being monitored
23:44:20  <kostco>https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent
23:44:59  <kostco>the coding style varies a lot in that repo so headsup
23:45:40  <kostco>heres an example with streams being used within a bit that was written before which relies on a callback on completion
23:45:40  <kostco>https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent/blob/master/hostinfo/autoupdates.lua
23:46:13  * dan336quit (Quit: Leaving.)