01:23
<TimothyGu>
Is https://github.com/tc39/proposal-javascript-standard-library/ still being actively developed?
01:58
<devsnek>
TimothyGu: i believe that turned into https://github.com/syg/standard-library-task-group
02:00
<shu>
devsnek: no, SLTG is not directly related to the standard library proposal. in fact SLTG turned more into the "incubator calls"
02:00
<devsnek>
hmm ok
02:01
<shu>
TimothyGu: the standard library proposal turned into builtin modules, since that's required for how michael saboff and co at JSC want to do the standard library
02:01
<shu>
TimothyGu: it's still being worked on by them (and me to a much smaller extent). there are thorny technical issues with polyfilling and making the available to non-module code that aren't solved yet
02:02
<shu>
making them*
02:02
<devsnek>
I'm not a fan of modules for standard library
02:02
<TimothyGu>
ah
02:03
<shu>
yeah, i'm also of the opinion, as domenic pointed out, if new standard library features were only builtin modules and builtin modules aren't available to script, that arbitrary bifurcates the ecosystem
02:03
<shu>
so it's pretty important that there be a way for builtin modules to be available to script
02:04
<devsnek>
has that been figured out yey
02:04
<devsnek>
yet
02:04
<shu>
nope, it's pretty hard
02:04
<devsnek>
yeah I'm of the opinion it's better to just keep making globals
02:04
<shu>
the availability-to-script thing is also the crux of it for ljharb's position that they must be polyfillable as well
02:05
shu
off for the night
02:05
<devsnek>
👋
02:09
<TimothyGu>
what's wrong about `import()`
02:14
<devsnek>
TimothyGu: not sync
02:14
<TimothyGu>
ah that
02:19
<devsnek>
i'm so excited for tla
16:17
<rwaldron>
@shu https://github.com/tc39/proposal-atomics-wait-async/issues/28
16:17
<shu>
rwaldron: thanks for ping, in mtgs until 11am PT, will look in afternoon
16:18
<rwaldron>
Thank you!
16:20
<rwaldron>
also, cc @ljharb
16:23
<ljharb>
commented
17:49
<rwaldron>
ljharb thank you!