00:00:00 --- log: started retro/13.02.11
05:57:38 --- quit: zachk (Quit: WeeChat 0.3.7)
06:59:57 --- quit: erider (Ping timeout: 245 seconds)
07:07:20 --- quit: tangentstorm (Ping timeout: 276 seconds)
07:07:55 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #retro
08:26:13 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #retro
09:45:39 --- join: Mat2 (~claude@91-65-144-133-dynip.superkabel.de) joined #retro
09:45:54 <Mat2> salut !
09:54:44 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro
12:45:11 --- join: impomatic (~digital_w@47.204.125.91.dyn.plus.net) joined #retro
12:49:18 --- quit: kumul (Quit: Leaving)
12:52:10 <Mat2> sah, I see an metro welcome message and promt
13:54:38 <tangentstorm> hey, congrats, Mat2 :)
13:56:28 <tangentstorm> I don't know what I've done to ngaro.js.
13:57:12 <tangentstorm> My fork no longer works in firefox, and has odd behavior in chrome.
13:57:42 <tangentstorm> I know the revision where I introduced the problem for firefox, but I have no idea what the problem actually is.
13:59:10 <tangentstorm> None of the tests I've written expose it, and everything I've looked at appears to be identical between the two browsers.
14:04:31 <tangentstorm> I think I'm going to just rebuild it from the ground up, one procedure at a time.
14:31:21 --- quit: ncv (Remote host closed the connection)
14:48:44 <Mat2> hmm, one possible problems are implementation specific details of the JIT compilers
14:49:02 <Mat2> ^problem
15:21:32 --- join: kumul (~Kumool@76.26.237.95) joined #retro
16:44:14 <Mat2> ciao
16:44:21 --- quit: Mat2 (Quit: Verlassend)
16:52:27 --- quit: kumul (Ping timeout: 245 seconds)
17:00:52 --- join: kumul (~Kumool@c-76-26-237-95.hsd1.fl.comcast.net) joined #retro
17:29:59 --- join: kumool (~Kumool@76.26.237.95) joined #retro
17:32:33 --- quit: kumul (Ping timeout: 248 seconds)
17:59:07 --- quit: kumool (Ping timeout: 245 seconds)
23:59:59 --- log: ended retro/13.02.11