09:03:49  * xaxxonquit (Read error: Connection reset by peer)
09:05:16  * xaxxonjoined
09:30:44  * xaxxonquit (Quit: xaxxon)
09:44:47  * thefourtheyequit
09:45:01  * thefourtheyejoined
09:56:05  * plutoniixquit (Quit: Leaving)
09:57:18  * xaxxonjoined
10:01:07  * xaxxonquit (Client Quit)
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:42  * mylesborinsjoined
10:49:09  * mostynbjoined
11:05:10  * Net147quit (Quit: Quit)
11:07:41  * Net147joined
13:36:59  * unixpicklejoined
13:55:05  * bradleymeckjoined
13:59:26  * Kronuzquit (Quit: I'll be back...)
14:06:31  * Kronuzjoined
14:08:03  * plutoniixjoined
14:18:04  * mostynbquit (Quit: x)
14:29:29  * Kronuzquit (Quit: I'll be back...)
14:36:04  * Kronuzjoined
14:47:56  * Kronuzquit (Quit: I'll be back...)
14:49:34  * Kronuzjoined
14:50:33  * Kronuzquit (Remote host closed the connection)
15:08:31  * Kronuzjoined
15:09:47  * seventhjoined
15:27:48  * bradleymeckquit (Quit: bradleymeck)
15:38:01  * bradleymeckjoined
15:38:01  * bradleymeckquit (Client Quit)
15:48:27  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:46:09  * bradleymeckjoined
16:50:03  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
17:01:13  * bradleymeckquit (Quit: bradleymeck)
17:03:58  * bradleymeckjoined
17:16:16  * unixpicklejoined
17:36:56  * Venemojoined
17:38:34  * bradleymeckquit (Quit: bradleymeck)
17:53:25  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
18:12:34  * bradleymeckjoined
18:28:34  * seventhquit (Remote host closed the connection)
18:31:54  * unixpicklejoined
18:48:27  * Venemoquit (Quit: Communi 3.5.0 - http://communi.github.com)
19:42:41  * Venemojoined
19:42:43  * Venemoquit (Client Quit)
19:52:07  <caitp>daurnimator: those benchmarks are not as useful as you might think they are
19:53:16  <caitp>if the code you're writing isn't perf critical, you should use the one you prefer to read/write. if it is perf-critical, use the one that works better in your particular application
19:56:32  <caitp>the Object.freeze benchmark is flawed for other reasons. Object.freeze/seal being called in a loop goes through every property in your object, and makes it read-only (and possibly non-configurable, depending on the integrity level), and then sets a bit in the object's Map
19:56:46  <caitp>doing that many times in a loop is of course quite expensive
19:59:52  <caitp>it might be possible to speed up Object.freeze/seal to cheat that particular benchmark in js-create-lowering, though. not sure if that would be worth doing, I don't think anything actually does this in practice
21:03:43  * bradleymeckquit (Quit: bradleymeck)
21:37:09  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
21:37:52  * Guest59joined
21:37:56  * Guest59quit (Client Quit)
21:51:16  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:29:21  * Guest59joined
22:46:02  * RT|Chatzillajoined
22:51:52  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:55:05  * Guest59joined
23:11:06  * unixpicklejoined
23:25:45  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:30:21  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:32:18  * Guest59joined
23:46:42  * unixpicklejoined
23:58:45  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:59:23  * Guest59joined