2025-10-01 [10:31:13.0314] Any further details on the 2026 agenda? We need to lock down the week for a company event in January and really need it not to conflict with plenary. [10:33:30.0886] * Any further details on the 2026 agenda? We need to lock down the week for a company event in January and really need it not to conflict with plenary. Edit: Well I was just told our event week was decided. Let's hope there is no plenary week of Jan 12 [10:48:28.0570] * Any further details on the 2026 agenda? We need to lock down the week for a company event in January and really need it not to conflict with plenary. Edit: Well I was just told our event week is about to be decided. Let's hope there is no plenary week of Jan 12 (the most likely candidate so far) 2025-10-02 [07:43:34.0971] first 2026 meeting is Jan 20-22 [08:35:50.0241] Virtual, right? Or so at least I understood from the discussion at the very end of the plenary. [08:36:05.0046] Yes [08:36:06.0543] yes, remote-only [09:40:43.0938] I've got a couple of `TypedArray`-related proposals for the agenda next month in Tokyo that I'm looking forward to presenting. Slides are here if anyone wants to get a head start: https://docs.google.com/presentation/d/1RIhMpf4gY2wX0KZcmCUU6i9l9Ay7WBu0vY4vIsJUwTg/edit?slide=id.p#slide=id.p .. We can save discussion for the plenary, just wanted to provide a heads up. [09:41:30.0642] * I've got a couple of `TypedArray`-related proposals for the agenda next month in Tokyo that I'm looking forward to presenting. Slides are here if anyone wants to get a head start: https://docs.google.com/presentation/d/1RIhMpf4gY2wX0KZcmCUU6i9l9Ay7WBu0vY4vIsJUwTg/edit?slide=id.p#slide=id.p .. We can save discussion for the plenary, just wanted to provide a heads up. These would be for Stage 1 consideration. [09:46:48.0053] James M Snell: nice. Some feedback: for stage 1 it helps to establish motivation for solving the problem, ideally with several examples. The WritableStream one is good but could use more, others need them too. I think this is especially true for swap16 etc because I can't imagine many applications which would want that and just "this API exists elsewhere" isn't a good enough reason without establishing it does something people need to do [09:49:41.0088] Yeah, over the next week or two I plan to fill in more of those details. The key ones I'm looking to get to Stage 1 now are the concat and find within, so I'll be focusing on those. The others are more background that I'll likely push for later. Mostly included those for additional context tho.... I'd really like to replace most of the use cases for Buffer [09:51:07.0996] the swapN functions are fairly specialized and I've only seen them used in very limited cases so those I can easily see not moving forward on [11:32:12.0052] I wish TCQ had a route to having a meeting where the attendees didn’t need to log in. So many TCs would benefit from this tool but GitHub is a bridge too far for the old guard [11:33:41.0269] oh boy do I have the solution for you! [11:36:28.0620] Aki: https://docs.google.com/spreadsheets/d/1xBUuIdmA3f4nY_PsesZfsolGAGnpfop7sxovyGmfM_U/edit?usp=sharing [11:40:03.0912] in this TYOOL 2025 they still can't handle having a github account? O.o [13:19:21.0484] I'm interested in discussing https://github.com/tc39/proposal-error-capturestacktrace at an upcoming TG3, who should I speak to about getting added to the agenda? [13:20:17.0598] I can scribble you in next week. The conveners lurk in #tc39-tg3-security:matrix.org. [14:50:19.0677] I've expanded the concat discussion with a couple more good examples and a link to some prior art based on `Buffer` that sees about 45m+ downloads a week as a reference point 2025-10-03 [22:35:17.0403] These people come from very different backgrounds from the people you're used to working with. Many still work in Word docs with track changes on. [07:06:35.0540] lol I assumed TYOOL was the name of a committee or a conference at first [08:10:17.0176] then `TCQ.xlsx` will be a revelation! [08:14:08.0570] omg Chris there's still a Word document put together by IEC in the early 2000s that includes a TABLE that SDOs use to make comments on each other's standards. They warn against changing the table column widths bc then when they compile all the comments they don't match [08:15:55.0523] nice [08:17:24.0776] Yea, verily, the _Old Ways_ offer a beacon of hope in this dark and uncertain times. [08:18:09.0288] * Yea, verily, the _Old Ways_ offer a beacon of hope in these dark and uncertain times. 2025-10-04 [19:23:54.0341] python gets lazy module loading https://pep-previews--4622.org.readthedocs.build/pep-0810/ [20:04:52.0430] * python proposal for lazy module loading https://pep-previews--4622.org.readthedocs.build/pep-0810/ [00:36:39.0897] Nice! There was this one before: https://peps.python.org/pep-0690/ which was opt-out instead of opt-in. But was rejected. This new one being opt-in (if I'm reading correctly) aligns with how we've approached import-defer