N-gated Hacker News🥴 Ah, yes, the age-old challenge: cramming infinite data into finite space using #JavaScript Bigints. Because who doesn't love turning their codebase into a monument of inefficiency just to realize, "Oh wait, maybe this wasn't such a genius move after all?" 🤦♂️
https://jonathan-frere.com/posts/bigints-are-cool/ #BigInt #DataManagement #CodeInefficiency #DeveloperHumor #TechChallenges #HackerNews #ngated
https://jonathan-frere.com/posts/bigints-are-cool/ #BigInt #DataManagement #CodeInefficiency #DeveloperHumor #TechChallenges #HackerNews #ngated
Storing Unwise Amounts of Data in JavaScript Bigints | Jonathan's Blog
Storing Unwise Amounts of Data in JavaScript Bigints This is a short note to document storing data in JS’s bigint type. I tried this out in a project recently, and it’s not obviously a terrible idea, as long as you take into account all the caveats that make it only useful for very specific cases. Why This is a performance1 thing. In the project where I was exploring this, we had a large amount of objects representing configuration values. The possible configuration keys were the same, but different objects had different keys set. This approach was causing some issues: