00:44:52  * ningujoined
00:46:41  <ningu>is there a particular reason that the ecma standard is 262 and the committee is 39?
00:48:04  <ningu>ok, I see that ECMA has various standards, so it makes sense 262 is only one of them
00:48:09  <ningu>but does it have other technical committees? :P
00:48:33  <ningu>apparently it does
00:56:38  * ninguquit (Quit: Lost terminal)
00:56:56  * AtumTquit (Quit: AtumT)
02:04:00  <devsnek>react hooks got me thinking
02:04:13  <devsnek>what if there was a way to expose the location of a call expression as a symbol or something
02:04:44  <devsnek>a while ago I made a little clone of hooks that uses tagged templates to this effect but it's obviously a strange api
02:05:57  <devsnek>maybe react hooks are just a bad api and this is a silly topic but imo it does show off some interesting design patterns
03:00:06  * gibson042quit (Ping timeout: 252 seconds)
04:33:41  * jmdyckquit (Remote host closed the connection)
04:34:29  <ljharb>the requirement to call them in the same unconditional order imo is a bad API design
12:08:42  * AtumTjoined
12:27:00  * jmdyckjoined
14:14:40  * ephemera_joined
14:20:18  * ephemera_quit (Read error: Connection reset by peer)
14:20:22  * ephemera__joined
14:26:15  * ephemera__quit (Read error: Connection reset by peer)
14:26:22  * ephemera_joined
14:32:09  * ephemera_quit (Read error: Connection reset by peer)
14:32:24  * ephemera_joined
14:38:17  * ephemera_quit (Read error: Connection reset by peer)
14:38:24  * ephemera_joined
14:44:18  * ephemera_quit (Read error: Connection reset by peer)
14:44:26  * ephemera_joined
14:50:12  * ephemera_quit (Read error: Connection reset by peer)
14:50:26  * ephemera_joined
14:54:41  * ephemera_quit (Ping timeout: 258 seconds)
23:35:31  * keith_millerjoined