00:05:07  * shykeschanged nick to zz_shykes
00:09:29  * mikealquit (Quit: Leaving.)
00:10:17  * TheJHquit (Ping timeout: 245 seconds)
00:30:05  * zz_shykeschanged nick to shykes
00:32:28  * shykeschanged nick to zz_shykes
00:58:10  * simcop2387quit (Excess Flood)
00:58:33  <rowbit>Hourly usage stats: [free: 4]
01:00:08  * simcop2387joined
01:17:38  * zz_shykeschanged nick to shykes
01:18:25  * shykeschanged nick to zz_shykes
01:41:59  * stlsaintjoined
01:50:07  * stlsaintquit (Ping timeout: 252 seconds)
01:52:07  * stlsaintjoined
01:58:33  <rowbit>Hourly usage stats: [free: 17]
02:03:09  * wiwilliajoined
02:26:22  * darshanshankarquit (Quit: darshanshankar)
02:27:29  * ryan_stevensjoined
02:45:47  * ryan_stevensquit (Quit: Leaving.)
02:46:13  * ryan_stevensjoined
02:46:53  * wiwilliaquit (Ping timeout: 244 seconds)
02:58:32  <rowbit>Hourly usage stats: [free: 10]
03:17:56  * hij1nxjoined
03:33:06  * stlsaintquit (Ping timeout: 260 seconds)
03:34:51  * stlsaintjoined
03:43:12  <niftylettuce>my roommate building gmail replacement
03:43:15  <niftylettuce>im building attachment replacement
03:43:20  <niftylettuce>time to crush those effers
03:44:25  * zz_shykeschanged nick to shykes
03:45:29  * shykeschanged nick to zz_shykes
03:58:33  <rowbit>Hourly usage stats: [free: 10]
04:02:08  * amasadjoined
04:03:54  * amasadquit (Read error: Connection reset by peer)
04:04:13  * amasadjoined
04:11:35  <niftylettuce>SubStack: would you recommend seq or async module
04:11:42  <niftylettuce>chapel: ping
04:12:55  <chapel>depends on what you like
04:16:38  <niftylettuce>paul_irish: im addin a little whimsy 4 u
04:17:25  <niftylettuce>mothereffingwhimsys.com
04:26:41  * stlsaintquit (Ping timeout: 240 seconds)
04:28:42  * stlsaintjoined
04:47:45  * zz_shykeschanged nick to shykes
04:58:33  <rowbit>Hourly usage stats: [free: 3]
04:59:53  * ryan_stevensquit (Quit: Leaving.)
05:02:02  * wiwilliajoined
05:06:11  * wiwilliaquit (Ping timeout: 240 seconds)
05:06:45  * purrquit (Read error: Connection reset by peer)
05:06:46  * ecquit (Read error: Connection reset by peer)
05:06:54  * purrjoined
05:09:52  * purrquit (Remote host closed the connection)
05:09:56  * purrjoined
05:11:31  * purrquit (Remote host closed the connection)
05:11:35  * purrjoined
05:12:04  * stlsaintquit (Ping timeout: 264 seconds)
05:13:25  * stlsaintjoined
05:20:49  * amasadquit (Quit: amasad)
05:21:35  * darshanshankarjoined
05:35:36  * purrquit (Remote host closed the connection)
05:35:41  * purrjoined
05:39:34  * purrquit (Remote host closed the connection)
05:39:39  * purrjoined
05:58:33  <rowbit>Hourly usage stats: [free: 4]
06:00:19  * mikealjoined
06:01:06  * darshanshankarquit (Quit: darshanshankar)
06:11:17  * st_lukejoined
06:17:01  * st_lukequit (Remote host closed the connection)
06:17:35  * st_lukejoined
06:21:15  * devaholicjoined
06:21:57  * st_lukequit (Ping timeout: 245 seconds)
06:33:27  * isaacsquit (Remote host closed the connection)
06:42:11  * rannmannquit (Ping timeout: 240 seconds)
06:42:22  * tm604joined
06:45:36  * TheJHjoined
06:51:18  <SubStack>bwahaha zygote is working
06:51:23  <SubStack>going to demo this at node philly
06:53:43  * darshanshankarjoined
06:55:39  <SubStack>darshanshankar: publishing an auto-balancing cluster experiment in just a bit
06:57:20  <darshanshankar>:O nice
06:58:14  <devaholic>node-disorder is trippy
06:58:32  <rowbit>Hourly usage stats: [free: 14]
06:58:44  <devaholic>just saw it
07:00:16  <devaholic>i like it though, except the regex match
07:00:28  <devaholic>i had a use for something like that just yesterday
07:01:00  <SubStack>I'm not actually using disorder anywhere
07:01:20  * stlsaintquit (Ping timeout: 246 seconds)
07:01:22  <SubStack>I just remembered that it was neat in haskell how you could not care about the order that expressions in the where or let clauses were ordered
07:01:44  <SubStack>and then dominic and some other folks were talking on irc about that kind of stuff and I felt like procrastinating
07:02:17  <devaholic>basically i had a series of functions that all take some time to execute, but only one of them was going to calculate the result that was going to be sent, but i cant know what that result is until they are all done, sooo either run them all in parallel and then do some routing or run them in a series and skip out when the right one is found
07:02:33  <devaholic>maybe not quite the same thing ^
07:03:13  * stlsaintjoined
07:03:14  <devaholic>it saves the user's time to run them in parallel i guess, but at the cost of cpu
07:03:29  <devaholic>but kind of depends
07:06:16  <SubStack>disorder isn't about async at all
07:06:21  <SubStack>it's all synchronous code
07:07:31  <devaholic>mmh
07:09:54  <darshanshankar>SubStack: is it on github yet?
07:10:05  <devaholic>disorder({ a: 1, b: 2, c: function (a) { return a*3 }, d: function (b) { return b*4 }})
07:10:23  <devaholic>c and d ?
07:10:50  <devaholic>i guess i didnt grok the whole code, but i assumed those would be parallel
07:11:48  <SubStack>darshanshankar: nope, one sec
07:13:34  <SubStack>https://github.com/substack/zygote
07:13:55  <SubStack>still fixing a bug with the de-allocation so it's not on npm yet
07:14:45  <darshanshankar>i see
07:16:32  <SubStack>but the idea is that you just tell the cluster how many of each type of service you need
07:16:41  <SubStack>and then the cluster figures out where to run everything
07:20:13  <SubStack>also service registries are the best thing ever
07:20:42  <devaholic>so it assumes all your stuff is in one repo then
07:21:10  <SubStack>yes
07:21:16  <SubStack>well
07:21:17  <SubStack>not really
07:21:23  <SubStack>this isn't repo-aware at all
07:21:40  <SubStack>you just put commands in the cluster.json to run things
07:21:42  <darshanshankar>i see
07:21:47  <SubStack>and it runs them everywhere
07:21:50  <SubStack>fleet is repo-aware
07:21:53  <darshanshankar>did you see BOSH btw?
07:22:00  <SubStack>negatory
07:22:11  <darshanshankar>https://github.com/cloudfoundry/bosh
07:23:40  <SubStack>wow they are not good at conveying the value proposition
07:24:38  <SubStack>oh neat though, they also think in terms of stem cells I see from their flow chart thing
07:24:39  <chapel>thats a huge project
07:24:47  <SubStack>yeah giant projects make me wince
07:26:34  <SubStack>looks like they are trying to solve a lot of problems
07:29:12  <chapel>I definitely think it could have been separated out
07:29:17  <chapel>at least some of the major parts
07:29:31  <chapel>maybe not as module as you do it SubStack
07:29:42  <chapel>but not some giant thing that makes no sense
07:30:19  <SubStack>well getting buy-in for massive pieces of infrastructure is hard
07:30:30  <SubStack>but using little pieces incrementally is pretty easy
07:31:42  <devaholic>but then you have to actually program things xD
07:34:18  * stlsaintquit (Ping timeout: 260 seconds)
07:35:45  * stlsaintjoined
07:42:56  <jesusabdullah>There's the Ikea approach
07:58:33  <rowbit>Hourly usage stats: [free: 2]
07:59:22  <SubStack>hooray everything works
07:59:27  <SubStack>now writing a simple test
07:59:29  <SubStack>then publishing
08:29:36  * darshanshankarquit (Quit: darshanshankar)
08:34:04  <niftylettuce>\o/
08:43:45  <niftylettuce>octocat is proud
08:44:01  <niftylettuce>$ cat octo -input james
08:58:32  <rowbit>Hourly usage stats: [free: 11]
09:10:41  <SubStack>now up on npm
09:10:43  <SubStack>https://github.com/substack/zygote
09:22:57  <devaholic>SubStack: does zygote make it no longer necessary to write any central seaport code? just to register in web.js, auth.js etc?
09:23:55  <devaholic>im pretty happy just using fleet for deployment but it looks useful
09:30:31  <SubStack>central seaport code?
09:31:28  <SubStack>with zygote you just tell the cluster how much of each type of service it needs to run and then the drones run the processes
09:58:33  <rowbit>Hourly usage stats: [free: 4]
10:13:20  * shykeschanged nick to zz_shykes
10:58:33  <rowbit>Hourly usage stats: [free: 12]
11:58:33  <rowbit>Hourly usage stats: [free: 14]
12:58:32  <rowbit>Hourly usage stats: [free: 26]
13:12:15  * mikealquit (Quit: Leaving.)
13:55:47  <SubStack>beep boop
13:58:32  <rowbit>Hourly usage stats: [free: 10]
14:13:00  * amasadjoined
14:16:27  * amasadquit (Client Quit)
14:53:55  * TheJHquit (Ping timeout: 256 seconds)
14:54:27  * hij1nxquit (Quit: hij1nx)
14:56:02  * TheJHjoined
14:58:33  <rowbit>Hourly usage stats: [free: 11]
15:24:29  * hij1nxjoined
15:52:20  * rannmannjoined
15:58:32  <rowbit>Hourly usage stats: [developer: 1, free: 26]
16:06:23  * hij1nxquit (Quit: hij1nx)
16:21:10  * TheJHquit (Ping timeout: 248 seconds)
16:36:42  * isaacsjoined
16:37:18  * rannmannquit (Read error: Connection reset by peer)
16:37:56  * rannmannjoined
16:42:05  * hij1nxjoined
16:43:43  * TheJHjoined
16:54:00  * rannmannquit (Read error: Connection reset by peer)
16:58:33  <rowbit>Hourly usage stats: [developer: 5, free: 19]
17:02:12  * hij1nxquit (Quit: hij1nx)
17:14:46  * amasadjoined
17:20:07  * rannmannjoined
17:20:08  * rannmannquit (Changing host)
17:20:08  * rannmannjoined
17:33:05  * rannmannquit (Quit: No one is so old as those who have outlived enthusiasm. - Henry David Thoreau)
17:33:15  * st_lukejoined
17:41:07  * rannmannjoined
17:43:56  * stlsaintquit (Ping timeout: 245 seconds)
17:45:47  * stlsaintjoined
17:58:32  <rowbit>Hourly usage stats: [free: 30]
18:19:41  * st_lukequit (Remote host closed the connection)
18:31:43  * maxogdenquit (Ping timeout: 260 seconds)
18:35:13  * antixquit (Ping timeout: 260 seconds)
18:35:13  * ircretaryquit (Ping timeout: 260 seconds)