00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:09  * ircretaryjoined
00:00:41  * mikealquit (Quit: Leaving.)
00:00:59  * inolenjoined
00:01:32  <MI6>libuv-master-gyp: #320 UNSTABLE smartos-ia32 (3/198) windows-x64 (6/197) smartos-x64 (4/198) windows-ia32 (5/197) http://jenkins.nodejs.org/job/libuv-master-gyp/320/
00:02:06  * mikealjoined
00:09:23  * dshaw_joined
00:09:50  * jmar777joined
00:10:42  * kazuponquit (Ping timeout: 252 seconds)
00:11:24  * c4miloquit (Remote host closed the connection)
00:13:35  * c4milojoined
00:17:37  * mikealquit (Quit: Leaving.)
00:17:49  * st_lukequit (Remote host closed the connection)
00:18:15  * mikealjoined
00:20:01  <trevnorris>tjfontaine: so, have an example solution: https://github.com/joyent/node/issues/6623#issuecomment-29672275
00:21:32  <trevnorris>isaacs: ^
00:21:39  <tjfontaine>which test fails, i'm kinda worried about this state tracking like that
00:22:16  * dshaw_quit (Quit: Leaving.)
00:22:36  <trevnorris>test-stream2-writable.js L145: assert(tw._writableState.length >= 50);
00:22:59  * mikealquit (Ping timeout: 272 seconds)
00:22:59  <tjfontaine>ah, so you're deferring too early?
00:23:28  <trevnorris>when I console.log it the first 3 times it passes.
00:23:32  <trevnorris>but then fails on the 4th
00:24:26  <trevnorris>ran the patch through all my benchmarks and doesn't cause any performance hit, and memory usage when writing very small messages (e.g. < 1KB) is much much better
00:24:34  * jmar777quit (Remote host closed the connection)
00:25:03  <trevnorris>but the sync callback thing is a pain because _write{v} are what's calling the callback.
00:25:11  <tjfontaine>indeed
00:49:55  * mikealjoined
00:54:14  * mikealquit (Ping timeout: 240 seconds)
00:57:13  <tjfontaine>goddamn github
00:57:22  <tjfontaine>it would be nice if I could fucking close an issue right now
00:57:30  <tjfontaine>or comment
00:57:46  <tjfontaine>Failed to load resource: the server responded with a status of 422 (Unprocessable Entity)
00:58:22  * c4miloquit (Remote host closed the connection)
01:01:36  <trevnorris>tjfontaine: you have an example of why people like _need_ spawn/exec sync?
01:02:19  <tjfontaine>build scripts mostly, for people who like to replace shell scripting with node
01:02:21  <tjfontaine>more or less
01:03:30  <trevnorris>ah, ok. thanks
01:07:22  * kazuponjoined
01:10:12  * indexzeroquit (Quit: indexzero)
01:13:21  * wwicksquit (Quit: wwicks)
01:15:07  <inolen>trevnorris: I have a back burner task to make the tickprocessor run properly in node, and to do so it'd be helpful to have an execSync to properly emulate some of the d8 environment (https://github.com/bnoordhuis/node-profiler/blob/master/tools/v8/tickprocessor.js#L628)
01:15:35  <inolen>(just an example)
01:16:11  <trevnorris>inolen: ah, thanks for the example. :)
01:16:21  * acrichtojoined
01:16:42  * abraxasjoined
01:17:35  <acrichto>I recently ran into a problem where I have thousands of connections idle in the FIN_WAIT_1 state, (after my program has completely exited), and now my system apparently ran out of ephemeral ports? Has this been seen before or do others know what would cause something like this to happen?
01:18:04  <mmalecki>acrichto: did you increase number of ephemeral ports?
01:18:22  <mmalecki>acrichto: how do your TCP settings look like? you have socket reuse/recycle enabled?
01:18:51  <acrichto>mmalecki: hm, I have not yet tried increasing the number, and I'm not really sure what tcp settings to look at (on osx), did you have specific ones in mind?
01:19:12  <mmalecki>oh, this is OS X
01:19:12  <mmalecki>?
01:19:33  <acrichto>yes, ah and I just raised the ephemeral port limit and was able to get a connection through
01:19:43  <acrichto>the range was 49152 -> 65535
01:20:15  <mmalecki>yeah, that. if you're running this in production, you probably also want to enable socket reuse/recycle
01:20:42  <acrichto>I'm just running stress tests locally right now, just wondering why all of these ports are stuck open
01:20:55  <acrichto>I thought that they were all closed correctly, but maybe not?
01:21:28  * abraxasquit (Ping timeout: 264 seconds)
01:22:34  <mmalecki>acrichto: so FIN_WAIT_1 means waiting for the peer to ACK the FIN which was just sent to it
01:22:57  <mmalecki>acrichto: it can persist for 2 minutes on Linux
01:23:09  <acrichto>hm, woul something like that happen if uv_close wasn't called on the server side?
01:24:41  <mmalecki>acrichto: yes, I think this could happen if you didn't call uv_close and the receiving side died for example
01:25:24  <acrichto>hm, sounds like I need to figure out why uv_close isn't being called, thanks for the help!
01:25:39  <mmalecki>acrichto: http://www.tcpipguide.com/free/t_TCPConnectionTermination-2.htm has better explanation
01:25:51  <mmalecki>acrichto: with all the states, etc
01:26:08  <mmalecki>acrichto: and you get 80s' website flashback for free
01:26:18  <acrichto>oh man that's intense
01:27:07  <mmalecki>acrichto: the Client - Server stuff there can also go the other way around
01:27:25  <acrichto>do you know if there's a way to "flush out" all the FIN_WAIT_1 connections?
01:28:28  * abraxasjoined
01:32:41  * timoxleyquit (Remote host closed the connection)
01:32:44  <groundwater>trevnorris: tjfontaine are you free any time during nodesummit to talk async-listener performance or event-emitter listeners?
01:32:58  <tjfontaine>yup
01:33:00  <mmalecki>acrichto: no idea about flushing out FIN_WAIT_1 unfortunately
01:33:10  * dap_quit (Quit: Leaving.)
01:33:42  <groundwater>tjfontaine: trevnorris i don't actually have a ticket, but i can meet you somewhere outside
01:33:51  <groundwater>coffee etc.
01:33:59  <mmalecki>acrichto: there isn't too much info about FIN_WAIT_1 causing problems actually...
01:34:28  <acrichto>mmalecki: yeah the best I've been able to find is apparently /etc/init.d/networking restart (at least on linuxes)
01:34:37  <trevnorris>groundwater: sure. though I totally forgot I'm giving two talks. so trying to get everything done. :P
01:34:42  <tjfontaine>groundwater: I'll be at newrelic event
01:35:04  <groundwater>trevnorris: are you coming to New Relic tuesday night?
01:35:50  <trevnorris>groundwater: so, sorry.
01:36:23  <tjfontaine>*no I presume
01:36:31  <trevnorris>heh, yeah.
01:36:54  <groundwater>heh, no worries
01:37:11  <tjfontaine>I'm not sure what my schedule during the day actually is, but where is your office in relation to the event?
01:37:12  <groundwater>trevnorris: why don't i find you *after* your talks
01:37:22  * mikealjoined
01:37:55  <trevnorris>groundwater: sure
01:38:04  * trevnorrisgoes looking for his presentation times
01:38:40  <trevnorris>groundwater: ok. my second talk will be over on Wed around 3:45-ish
01:40:08  <groundwater>tjfontaine: it's not close, but i don't mind dropping by
01:40:40  * kazuponquit (Ping timeout: 246 seconds)
01:41:04  <groundwater>trevnorris: i'll come by then i guess
01:41:17  <groundwater>i'll come prepared with flamegraphs!
01:41:38  <othiym23>FLAAAAAAAME GRAAAAAAAAPHS
01:41:38  <LOUDBOT>ELLION GONZALES WAS REALLY MICHAEL JACKSON'S LOVER
01:42:18  <trevnorris>heh
01:43:02  <trevnorris>groundwater: i might have an extra ticket if you want to come.
01:47:13  <groundwater>trevnorris: i may take you up on that for wed
02:02:46  * trevnorris&
02:02:46  <LOUDBOT>BUT I GOTTA KNOW IF THEYRE MY FRIENDS
02:23:47  * jmar777joined
02:27:02  * c4milojoined
02:27:11  * inolenquit (Quit: Leaving.)
02:37:04  * kazuponjoined
02:40:30  * timoxleyjoined
02:41:54  * mikealquit (Quit: Leaving.)
02:55:36  * jmar777quit (Remote host closed the connection)
03:00:29  * TooTallNatequit (Quit: Computer has gone to sleep.)
03:00:38  * ircretaryquit (Remote host closed the connection)
03:03:05  * TooTallNatejoined
03:05:20  * timoxleyquit (Ping timeout: 265 seconds)
03:06:50  * kazuponquit (Ping timeout: 264 seconds)
03:07:05  * timoxleyjoined
03:08:05  * abraxasquit (Remote host closed the connection)
03:16:13  * abraxasjoined
03:17:17  * ircretaryjoined
03:31:43  * inolenjoined
03:36:36  * indexzerojoined
03:48:39  * kevinswiberjoined
03:53:05  * kazuponjoined
03:55:25  * skabbesquit (Quit: skabbes)
04:00:09  * indexzeroquit (Quit: indexzero)
04:01:30  * TooTallNatequit (Quit: Computer has gone to sleep.)
04:15:35  * defunctzombiechanged nick to defunctzombie_zz
04:19:17  * kevinswiberquit (Remote host closed the connection)
04:23:54  * kevinswiberjoined
04:31:17  * LOUDBOTquit (Ping timeout: 246 seconds)
04:37:18  * LOUDBOTjoined
04:37:39  * philipsquit (Excess Flood)
04:38:25  * philipsjoined
04:50:38  * kevinswiberquit (Remote host closed the connection)
05:04:10  * kazupon_joined
05:04:35  * kazuponquit (Ping timeout: 260 seconds)
05:11:52  * otwoquit (Quit: ~ Trillian Astra - www.trillian.im ~)
05:33:33  * kazupon_quit (Read error: Connection reset by peer)
05:33:54  * kazuponjoined
05:36:15  * mcavage_joined
05:36:15  * mcavagequit (Read error: Connection reset by peer)
05:38:53  * c4miloquit (Remote host closed the connection)
05:45:33  * abraxasquit (Remote host closed the connection)
05:54:18  * bradleymeckjoined
06:04:40  * mikealjoined
06:08:30  * wolfeidauquit (Remote host closed the connection)
06:28:09  * m76joined
06:28:52  * abraxasjoined
06:35:33  * mcavagejoined
06:35:33  * mcavage_quit (Read error: Connection reset by peer)
06:36:50  * paddybyersjoined
06:40:50  * indexzerojoined
06:41:23  <MI6>nodejs-v0.10-windows: #357 UNSTABLE windows-ia32 (10/605) windows-x64 (11/605) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/357/
06:45:52  <hueniverse>othiym23: did you get the book?
06:52:24  * wolfeidaujoined
06:55:22  * loladiroquit (Quit: loladiro)
07:03:21  * wolfeidauquit (Remote host closed the connection)
07:04:46  * wolfeidaujoined
07:19:01  * bajtosjoined
07:32:22  * wolfeidauquit (Remote host closed the connection)
07:34:21  * wolfeidaujoined
07:36:10  * acrichtopart
07:43:22  <othiym23>hueniverse: I was in Portland last week, so I haven't seen indexzero yet
07:43:34  <othiym23>I'll be at the thing tomorrow, though!
07:43:38  <othiym23>maybe the fates will align
07:44:13  <hueniverse>heh
07:45:03  <hueniverse>cool
07:45:14  <hueniverse>othiym23: you speaking tomorrow or wed?
07:46:58  <othiym23>hueniverse: Wednesday, in one of the lunchtime sessions
07:47:11  <hueniverse>sponsored?
07:47:12  <othiym23>curious to see what kind of turnout I get
07:47:35  <hueniverse>did you get the main stage?
07:48:10  <othiym23>nope, room 2
07:48:20  <othiym23>I'll be plugging hapi (among other things), though
07:48:26  <hueniverse>what are you agaist?
07:49:33  <hueniverse>looking
07:49:54  <hueniverse>I'll pimp it if I remember during my talk
07:51:03  <othiym23>it is for real the least technical talk I'll give this year
07:51:25  <othiym23>targeted more at business owners and project leads / managers than developers, even
07:52:11  * bradleymeckquit (Quit: bradleymeck)
07:53:24  <othiym23>(I said my JS.everywher talk was going to be nontechnical, and then spent 15 minutes talking about standards organizations, programming language theory, and committees 00 it seemed nontechnical to me at the time)
07:54:06  <othiym23>s/00/--/ && s/everywher/everywhere/ -- lotsa lag on my IRC box tonight
07:58:51  * rendarjoined
07:58:52  * rendarquit (Excess Flood)
08:16:22  * DarkGodWjoined
08:37:08  * inolenquit (Quit: Leaving.)
08:37:25  * inolenjoined
08:38:47  <creationix>oh my, this is not encouraging: http://www.linuxquestions.org/questions/linux-networking-3/too-many-fin_wait2-in-netstat-output-606724/
09:03:46  * hueniversequit (Quit: Leaving.)
09:09:19  * rendarjoined
09:13:38  * janjongboomjoined
09:14:01  * wolfeidauquit (Remote host closed the connection)
09:17:49  * indexzeroquit (Quit: indexzero)
09:45:39  * hzjoined
09:48:02  * stagasquit (Ping timeout: 246 seconds)
10:20:14  * janjongboomquit (Ping timeout: 240 seconds)
10:21:10  * janjongboomjoined
10:21:51  * kazuponquit (Remote host closed the connection)
10:31:32  * abraxasquit (Remote host closed the connection)
10:35:17  * hzquit
10:35:57  * janjongboomquit (Ping timeout: 272 seconds)
10:36:43  * janjongboomjoined
10:42:39  * hzjoined
10:49:28  <MI6>nodejs-v0.10: #1640 UNSTABLE smartos-x64 (6/605) smartos-ia32 (4/605) linux-x64 (1/605) http://jenkins.nodejs.org/job/nodejs-v0.10/1640/
11:03:40  * hzquit
11:04:28  <mmalecki>creationix: FIN_WAIT2 and CLOSE_WAIT hells are a special kind of a hell to be in
11:11:46  * wolfeidaujoined
11:12:07  <creationix>yeah
11:12:19  <creationix>it would be fine if fin_wait_timeout actually worked
11:12:19  * hzjoined
11:12:25  * bajtosquit (Quit: bajtos)
11:12:38  <creationix>but even when set to the default 60second timeout, the state persists for days or weeks
11:13:04  * hzquit (Client Quit)
11:51:16  <mmalecki>creationix: I think I'll test how different OSes handle FIN_WAIT_2
11:51:43  <mmalecki>creationix: since I recall SmartOS not being terrible at it (we never saw FIN_WAIT_2 persist for more than 2 minutes)
12:36:39  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
13:05:53  * mcavage_joined
13:05:54  * mcavagequit (Read error: Connection reset by peer)
13:06:20  * m76quit (Read error: Connection reset by peer)
13:08:03  * janjongboomjoined
13:36:34  * bradleymeckjoined
13:46:26  * defunctzombie_zzchanged nick to defunctzombie
13:58:56  * timoxleyquit (Remote host closed the connection)
14:02:49  * jmar777joined
14:04:06  * cjbjoined
14:05:07  * bajtosjoined
14:39:52  * kevinswiberjoined
14:52:40  * loladirojoined
14:53:41  * c4milojoined
14:55:57  * dshaw_joined
15:04:56  * pachetjoined
15:04:56  * pachetquit (Changing host)
15:04:56  * pachetjoined
15:07:34  * kevinswiberquit (Remote host closed the connection)
15:08:39  * m76joined
15:10:08  * loladiroquit (Quit: loladiro)
15:12:30  * kazuponjoined
15:21:29  <MI6>nodejs-master: #743 UNSTABLE osx-x64 (1/680) smartos-ia32 (7/680) smartos-x64 (8/680) osx-ia32 (1/680) http://jenkins.nodejs.org/job/nodejs-master/743/
15:25:05  * bradleymeck_joined
15:25:44  * dshaw_quit (Quit: Leaving.)
15:46:17  * AvianFlujoined
15:47:54  * DarkGodWquit (Read error: Connection reset by peer)
16:14:01  * mikealquit (Quit: Leaving.)
16:26:52  * mikealjoined
16:34:01  * abraxasjoined
16:34:22  * kevinswiberjoined
16:38:34  * mikealquit (Quit: Leaving.)
16:38:45  * abraxasquit (Ping timeout: 245 seconds)
16:43:49  * loladirojoined
16:48:14  * kevinswiberquit (Remote host closed the connection)
16:52:50  * kevinswiberjoined
16:53:22  * c4miloquit (Remote host closed the connection)
16:53:49  * loladiroquit (Quit: loladiro)
16:55:57  <isaacs>Probably goes without saying, but piscisaureus, tjfontaine, trevnorris, and I are at Node Summit, so no call today. indutny you can give yourself a status update, if you'd like :)
16:56:13  <isaacs>sblom AlexisMocha: Are you guys here?
16:56:13  <indutny>:)
16:57:25  <AlexisMocha>i am
17:00:46  <cjb>Hi, I'm looking for bugs to help out with, feel free to mention any that you'd like someone to look at. I'm new to libuv internals, would like to learn. (I'm also looking at the github issue list, of course, but it's hard to know which bugs are valid.)
17:01:03  * brsonjoined
17:07:20  <AlexisMocha>isaacs: ok so I guess no call today
17:08:35  * loladirojoined
17:09:02  * c4milojoined
17:10:31  * brycebariljoined
17:12:22  * TooTallNatejoined
17:15:30  * wavdedjoined
17:17:40  <isaacs>AlexisMocha: correct. but welcome! nice to meet you!
17:17:47  <isaacs>AlexisMocha: next week for sure :)
17:21:16  * inolenquit (Quit: Leaving.)
17:22:38  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:25:41  * c4miloquit (Remote host closed the connection)
17:30:30  * stagasjoined
17:30:45  * loladiroquit (Quit: loladiro)
17:41:03  * kellabytequit (Remote host closed the connection)
17:42:53  * loladirojoined
17:44:21  * wavdedquit (Quit: Nighty night)
17:48:17  * TooTallNatequit (Quit: Computer has gone to sleep.)
17:53:06  <MI6>libuv-master: #368 UNSTABLE windows (5/197) smartos (3/198) http://jenkins.nodejs.org/job/libuv-master/368/
17:56:10  * Kakerajoined
17:57:26  * loladiroquit (Quit: loladiro)
18:04:58  * TooTallNatejoined
18:05:47  * loladirojoined
18:07:57  * inolenjoined
18:11:25  * mikealjoined
18:12:03  <MI6>libuv-node-integration: #334 UNSTABLE osx-x64 (1/680) osx-ia32 (1/680) smartos-x64 (7/680) smartos-ia32 (5/680) http://jenkins.nodejs.org/job/libuv-node-integration/334/
18:17:01  * wavdedjoined
18:21:52  * AvianFluquit (Remote host closed the connection)
18:23:31  <creationix>is there a blocking (non event based) way to write to the terminal in node?
18:23:39  <creationix>I know console.error used to be sync for this reason
18:25:49  <mmalecki>creationix: stdio streams are still sync
18:27:46  <creationix>then why do they create event sources?
18:27:46  <creationix>I guess it's for API consistency since they are streams
18:28:16  * mcavage_quit (Remote host closed the connection)
18:29:23  * AvianFlujoined
18:32:41  * kazuponquit (Remote host closed the connection)
18:35:16  * abraxasjoined
18:39:46  * abraxasquit (Ping timeout: 245 seconds)
18:45:42  * wavdedquit (Quit: Nighty night)
18:46:57  * c4milojoined
18:47:09  * wavdedjoined
18:55:35  * felixgejoined
18:55:42  * felixgequit (Changing host)
18:55:42  * felixgejoined
18:57:18  * wavdedquit (Quit: Nighty night)
18:58:47  <felixge>isaacs: hi, yt?
18:58:49  * wavdedjoined
19:01:51  <felixge>isaacs: just got your e-mail. will reply there. just came in to see if you wanted to discuss
19:03:23  * kazuponjoined
19:09:09  <groundwater>creationix: require('fs').writeSync(1, message)
19:16:22  <creationix>neat idea
19:22:51  * loladiroquit (Quit: loladiro)
19:23:04  * mcavagejoined
19:24:15  * jmar777quit (Ping timeout: 272 seconds)
19:24:57  * mcavagequit (Remote host closed the connection)
19:25:11  * mcavagejoined
19:25:27  * mcavagequit (Remote host closed the connection)
19:26:11  * mcavagejoined
19:29:14  * bajtosquit (Quit: bajtos)
19:30:16  * loladirojoined
19:32:31  * felixgequit (Ping timeout: 260 seconds)
19:32:59  * kellabytejoined
19:34:08  * kazuponquit (Read error: Connection reset by peer)
19:34:24  * kazuponjoined
19:34:41  * jmar777joined
19:35:15  * felixgejoined
19:36:31  <groundwater>creationix: console.log will cause async events, so will process.stdout.write
19:36:56  <groundwater>because when working on async listener, it goes bananas if you use either within a listener
19:38:59  * swajquit (Remote host closed the connection)
19:40:10  * loladiroquit (Quit: loladiro)
19:43:26  <creationix>groundwater, I found a workaround that works pretty well and still lets me use console.log before: function (context, storage) {
19:43:26  <creationix> if (ignore || !storage) return;
19:43:26  <creationix> // ...\\
19:43:26  <creationix> }
19:43:30  <creationix>grr
19:43:37  <creationix>https://gist.github.com/creationix/7776192
19:50:58  * swajjoined
19:51:26  * felixgequit (Ping timeout: 246 seconds)
19:54:22  * felixgejoined
19:54:22  * felixgequit (Changing host)
19:54:22  * felixgejoined
19:57:36  * kenperkinsjoined
20:06:00  * jmar777_joined
20:06:05  * jmar777quit (Read error: Connection reset by peer)
20:07:30  * kazuponquit (Ping timeout: 245 seconds)
20:16:05  * kenperkinsquit (Quit: Computer has gone to sleep.)
20:19:23  * loladirojoined
20:19:31  * kenperkinsjoined
20:20:49  * loladiroquit (Client Quit)
20:22:08  * mikealquit (Quit: Leaving.)
20:23:51  * wavdedquit (Ping timeout: 260 seconds)
20:25:46  * kevinswiberquit (Remote host closed the connection)
20:27:26  * wavdedjoined
20:31:46  * kenperkinsquit (Quit: Computer has gone to sleep.)
20:34:04  * kenperkinsjoined
20:36:08  * abraxasjoined
20:40:26  * abraxasquit (Ping timeout: 246 seconds)
20:42:00  * loladirojoined
20:46:02  * c4miloquit (Ping timeout: 246 seconds)
20:46:17  * loladiroquit (Ping timeout: 252 seconds)
20:46:52  * c4milojoined
20:56:25  <groundwater>creationix: +1
21:01:44  <creationix>groundwater, currently I'm making a web framework that totally abuses async-listener to do things that people think are impossible
21:02:00  <creationix>like throw a string to send a response to the client
21:02:06  * c4miloquit (Remote host closed the connection)
21:02:12  <groundwater>creationix: you are the mad scientist of node
21:02:26  <creationix>and global request and response variables that auto-update depending on which event-chain you're currently in
21:02:34  <groundwater>creationix: i can't really say anything since NodeOS is my side project
21:02:40  <creationix>lol
21:02:43  <creationix>indeed
21:02:50  <groundwater>race you to the top of Mt. Crazy?
21:03:04  <creationix>:)
21:03:14  <creationix>I go there often, it's a nice place to camp
21:04:24  * kazuponjoined
21:05:08  <groundwater>creationix: are you at nodesummit?
21:07:01  * loladirojoined
21:07:05  * wavdedquit (Quit: Nighty night)
21:07:20  * loladiroquit (Client Quit)
21:11:14  * TooTallNatequit (Quit: Computer has gone to sleep.)
21:12:41  * wavdedjoined
21:20:47  * AndreasMadsenjoined
21:22:03  * paddybyersquit (Ping timeout: 272 seconds)
21:25:44  <creationix>groundwater, no, I'm in Italy
21:26:49  <dazld_>hey :)
21:27:05  <dazld_>creationix: throwing a string to send a response?
21:27:08  <dazld_>:D
21:27:57  <dazld_>the global req / res objects sounds interesting
21:28:32  * AndreasMadsenquit
21:29:07  * m76quit (Read error: Connection reset by peer)
21:30:52  * TooTallNatejoined
21:37:09  * jmar777_quit (Remote host closed the connection)
21:37:27  * kazuponquit (Ping timeout: 246 seconds)
21:39:27  * bradleymeck_quit (Quit: bradleymeck_)
21:41:50  * timoxleyjoined
21:44:58  <creationix>dazld_, yep, just finished the proof of concept. Putting in a gist now
21:45:12  <dazld_>neat, would be interested to see
21:46:13  * kenperkinsquit (Quit: Computer has gone to sleep.)
21:46:26  <creationix>dazld_, groundwater https://gist.github.com/creationix/7778005
21:47:49  <dazld_>line 48
21:47:56  <dazld_>ahah, does that work?
21:48:37  <dazld_>magic is the right word
21:49:01  <groundwater>async listeners are magical
21:49:13  <dazld_>+1 there
21:57:03  * brsonquit (Ping timeout: 246 seconds)
21:59:00  * brsonjoined
22:00:29  <othiym23>people would try to set me on fire if I made CLS work that way, creationix
22:00:35  <othiym23>they might even succeed
22:00:48  <dazld_>throw seems to be a reasonable verb choice for sending to the client
22:01:01  <dazld_>wait
22:01:32  <creationix>othiym23, :D
22:01:51  <othiym23>dazld_: you can basically treat 'throw' as a synonym for 'goto' in that gist
22:02:39  <dazld_>yep, with type checking figuring out what to do with it..
22:03:58  <othiym23>that is the most dynamic dispatch there
22:04:11  <othiym23>I guess creationix could add some self-modifying code
22:04:54  <dazld_>eval the thrown value could be fun
22:06:40  <creationix>throw, return, break and continue are *all* technically forms of goto
22:07:47  * pachetquit (Quit: leaving)
22:07:49  <othiym23>#6631 is a good find
22:08:09  <othiym23>creationix: yep, trying to deal with mutation + computed goto is a good summary for the last year
22:08:27  * AvianFlu_joined
22:08:33  <othiym23>*my* last year, at least
22:11:24  * AvianFluquit (Ping timeout: 246 seconds)
22:13:48  <othiym23>sorta seems like Node needs a fast version of slice somewhere in the util library to deal with things like #6631
22:16:20  * paddybyersjoined
22:17:18  <dazld_>might not work.. reading that issue, if you have a fast slice as a util function, then you would have to pass arguments to it
22:18:02  <dazld_>and calling a function with the arguments object seems to be the prob..?
22:18:10  * felixgequit (Quit: felixge)
22:19:38  <othiym23>dazld_: the utility function could be inlined, I think, but good point
22:19:48  * loladirojoined
22:19:50  <othiym23>jeez, something else to benchmark
22:19:54  <dazld_>:p
22:20:18  <dazld_>actually, a set of utils with best-for-v8 could be a cool thing
22:20:25  <othiym23>using a function is at least faster than using Array.prototype.siice.call / [].call on arguments
22:21:52  * mikolalysenkojoined
22:22:17  <othiym23>dazld_: https://github.com/joyent/node/pull/6278 is where I got the idea for using a standalone function for dealing with slicing arguments
22:26:40  <dazld_>f1?
22:28:27  <dazld_>looking at the jsperf, sorry
22:29:31  * felixgejoined
22:34:23  <dazld_>http://jsperf.com/while-vs-for/4
22:34:31  * kazuponjoined
22:36:38  <othiym23>weird how Chrome has been getting "slower" over time
22:36:51  <othiym23>I'd be interested to see the IRHydra output for those various V8 versions
22:36:55  * c4milojoined
22:36:56  * abraxasjoined
22:37:44  * skabbesjoined
22:40:38  * wavdedquit (Quit: Hasta la pasta)
22:41:11  * c4miloquit (Ping timeout: 246 seconds)
22:41:40  * abraxasquit (Ping timeout: 245 seconds)
22:43:48  * AvianFlu_changed nick to AvianFlu
22:45:43  * stagasquit (Ping timeout: 260 seconds)
22:47:16  * felixgequit (Quit: felixge)
22:47:47  * kevinswiberjoined
22:55:02  * mikealjoined
22:58:20  * bradleymeckquit (Quit: bradleymeck)
23:02:38  * TooTallNatequit (Quit: Computer has gone to sleep.)
23:06:23  * brsonquit (Ping timeout: 246 seconds)
23:07:28  * mikealquit (Quit: Leaving.)
23:07:41  * kazuponquit (Ping timeout: 245 seconds)
23:18:41  * bradleymeckjoined
23:18:45  * hzjoined
23:23:32  * stagasjoined
23:26:14  * skabbesquit (Read error: Connection reset by peer)
23:26:33  * skabbesjoined
23:29:28  * TooTallNatejoined
23:33:40  * rendarquit
23:37:31  * brsonjoined
23:39:59  * mcavagequit (Remote host closed the connection)
23:41:23  * hzquit
23:47:56  * AvianFluquit (Remote host closed the connection)
23:47:57  * timoxleyquit (Remote host closed the connection)
23:50:18  * `3Echanged nick to `3E|ZZZ
23:59:35  * brson_joined