01:00:12  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
01:05:20  * keith_millerjoined
01:19:40  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
01:21:25  * keith_millerjoined
01:56:12  <Domenic>My main objection is just aesthetic. In every single example the `@use: something foo` version looks verbose and awkward compared to the contextual keyword `something foo`.
01:57:01  <Domenic>Not the most helpful feedback, I know. But I'd be very reluctant to build any feature on this; the ergonomics just seem awkward.
02:05:37  <Domenic>Maybe if the prefix was `@@` instead of `@use: `
02:06:04  <Domenic>(and I know the word isn't always use, but honestly that just makes it more confusing, I think.)
02:08:22  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
02:20:05  * keith_millerjoined
02:34:40  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
02:36:07  * keith_millerjoined
05:22:02  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
05:37:50  * keith_millerjoined
05:39:24  * jmdyckquit (Remote host closed the connection)
05:45:58  * howdoijoined
06:41:13  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
06:42:08  * sebmckquit (*.net *.split)
06:42:08  * tschneidereitquit (*.net *.split)
06:42:26  * sebmckjoined
06:42:38  * tschneidereitjoined
07:04:53  * keith_millerjoined
07:39:17  * mgoljoined
07:57:54  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
08:51:27  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
08:52:19  * mgoljoined
09:07:02  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
11:18:36  * howdoiquit (Quit: Connection closed for inactivity)
12:08:53  * mgoljoined
12:51:48  <annevk>Is there a formal specification for Node.js's host semantics?
13:02:45  * jmdyckjoined
14:01:32  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
14:03:14  * mgoljoined
14:18:28  <bradleymeck>annevk: nope
14:18:50  <bradleymeck>annevk: are you looking for something in particular? The docs are the "specification" of sorts
14:19:17  <bradleymeck>but Node's semantics are more flexible/in flux than the web
14:20:27  <annevk>Yeah, that makes me wonder if it's a good idea to change the main specification without knowing whether the particular abstractions will turn out to be useful
14:21:58  <annevk>And the other oddity here is that Node.js only has a single implementation
14:22:18  <annevk>Which generally isn't sufficient for standards
14:29:55  <bradleymeck>annevk: maybe, but other locations are also doing in-process isolation, and this usage of shared intrinsics is not only being looked at by Node
14:30:47  <bradleymeck>see Agoric , CloudFlare , etc. None are browsers but they are doing stuff in-process, and they don't run on Node
14:31:12  <bradleymeck>what should we do if we have multiple projects looking at a feature but they are not in a shared runtime?
14:33:37  <annevk>I'm not sure, they all want new realms while reusing intrinsics? None of this seems particularly problematic btw, I'm just curious about some things.
14:34:02  <annevk>I'd love realm creation to be a little more explicit about what the host ends up providing, as the current abstract operation without arguments is rather puzzling.
14:34:54  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
14:37:39  * mgoljoined
14:42:29  <bradleymeck>@annevk I'd love to clean it up, but felt that shouldn't be in the PR
14:42:42  <bradleymeck>annevk: Agoric and Node are looking at that particular route
14:43:02  <bradleymeck>i don't think cloudflare is intending to have any multi-tenancy on same thread
14:44:31  <bradleymeck>I'd note that reusing intrinsics is very scary if you do not freeze things/censor paths to things. Things like getOriginals which allow always getting the realm intrinsics such as Date would be problematic for example for Agoric
16:44:33  * keith_millerjoined
16:45:08  * gibson042joined
16:51:05  <devsnek>this is pretty cool https://prop-tc39.now.sh/
16:52:52  * AtumTjoined
16:56:17  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:31:25  * keith_millerjoined
17:45:38  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:01:15  * keith_millerjoined
18:05:58  * keith_millerquit (Client Quit)
20:21:01  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:51:30  * mgoljoined
20:51:57  * mgolquit (Client Quit)
21:22:25  * MylesBorinsquit (Quit: farewell for now)
21:22:47  * MylesBorinsjoined
21:30:41  * mgoljoined
22:17:46  * akirosequit (Ping timeout: 250 seconds)
22:32:12  * akirosejoined
22:56:28  * mgolquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
23:01:25  * keith_millerjoined