| 00:27 | <shu> | i mean...... yeah? |
| 00:27 | <shu> | what's "bad" to you |
| 00:29 | <shu> | like do you care about running on 32-bit devices with smaller address spaces |
| 01:01 | <Kris Kowal> | HIMEM.SYS or bust. |
| 01:21 | <snek> | like if implementations are allocating the entire thing up front like a Vec::with_capacity call, then it would be bad |
| 01:21 | <shu> | i can only speak for chrome, and we just reserve the address space |
| 01:21 | <snek> | but if they're doing a virtual allocation its probably fine |
| 01:22 | <snek> | maybe we should put some guidance in the spec and in mdn |
| 01:22 | <shu> | HIMEM.SYS or bust. |
| 01:22 | <shu> | the spec has guidance |
| 01:22 | <snek> | oh does it |
| 01:22 | <snek> | i must have missed it |
| 01:23 | <shu> | https://tc39.es/ecma262/#sec-resizable-arraybuffer-guidelines |
| 01:23 | <snek> | oh nice |
| 01:23 | <snek> | i was looking down by the constructor |
| 01:24 | <shu> | also https://tc39.es/ecma262/#sec-growable-sharedarraybuffer-guidelines |
| 01:25 | <snek> | i'll use 2**30 in my code then |
| 01:25 | <snek> | sorry microcontrollers |
| 20:11 | <snek> | any temporal experts around? https://users.rust-lang.org/t/the-state-of-time-in-rust-leaps-and-bounds/107620/10 |
| 20:22 | <ptomato> | well, that was decided way before I became involved, but here's my take: compatibility with the underlying host is the most prominent reason. UTC has no leap seconds, and Unix time tracks UTC. also interoperability; network hosts everywhere use UTC timestamps without leap seconds. if you constantly have to translate between 'JS time' and 'host time'/'network time' that seems like a distinction that most programmers will ignore, and therefore an opportunity for discrepancies to creep in everywhere. not to mention that it obligates implementations to include a table of leap seconds that they must keep up to date, like the TZ data |
| 20:22 | <ptomato> | maybe someone who was there at the time can give more info |
| 21:31 | <jmdyck> | "UTC has no leap seconds"? UTC is precisely the time standard that has leap seconds. |
| 21:37 | <akaster> | Unix time buries its head in the sand and pretends they don't exist, requiring OS's to either add a discontinuity, or smear the leap second across many seconds |
| 21:37 | <ptomato> | you're right. sorry, I got confused with POSIX time. network time is POSIX time |