Let's go big
summary
Claim: JavaScript numbers hit Number.MAX_SAFE_INTEGER (2^53−1) so the talk builds several concrete systems to go beyond that: decimal strings up to to the power of 27 per safe string slot, binary/hex and 16‑bit string slots using Unicode code points, arrays limited by 2^32 - 1 length, and a streaming adder that reads one byte at a time (works on files larger than memory). Sizes quoted: ~268 MB per 16‑bit string, Node default ~1.7 GB, distributed sharding scales by machines; BigInt proposal is noted.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Numbers
- 3:47Why big numbers
- 5:12Converting to strings
- 7:54Addition and subtraction
- 10:35Multiplication and division
- 12:19Binary strings
- 14:20hexadecimal strings
- 15:43one character strings
- 18:09arrays
- 19:35memory
related talks
24mNative BigInts in JavaScript: A Case Study in TC39
05mBinary in JavaScript
20mJavaScript for Competitive Programming
27mEverything you never wanted to know about JavaScript numbers
11mThe secret life of Not-a-Number!
58mNumbers
26mDouble the Beyoncé: Navigating Numbers in JavaScript
50mThe Post JavaScript Apocalypse