Type suffixes on literals are fairly typical in languages using C-style syntax, so for JS I'd expect it to make more sense that way than doing it like Python does. Apart from the usual problems you'd get when your numbers suddenly behave very different than before. That has to be an opt-in syntax change.
I clicked expecting an article on a secret formula used by tupperware but was positively surprised by some pretty math in the morning. Nice breakdown, thanks!
I mean it's very good. I have some 25 year old Tupperware in my kitchen and it's still doing absolutely great. Glass eventually breaks, Tupperware plates live. Cheap boxes sometimes break in less than a year. It's worth buying for the longevity alone.
A lot of FUD articles use that word, and your first link is probably the most factual. But FYI the only Tupperware products that have had BPA are those made using polycarbonate (PC), which is a hard and brittle plastic very different from most of their products and not the first to come to mind upon mention of the brand; on the other hand, the semi-flexible containers they're most known for are PE/PP, which don't require plasticisers at all.
The meaning of digital data depends entirely on its interpretation. You can interpret a string of bits as an integer, a bitmap, machine instructions, text, etc. Once you have that idea firmly in mind, Tupper's formula doesn't feel any more surprising than e.g. the fact that the PDF spec is itself a PDF, or a physical book describing the process of bookbinding. It's self-referential, but not quite a quine.
> return d % 2n == 1n;
TIL(JavaScript): A BigInt is created by appending n to the end of an integer literal — 17n — or by calling the function BigInt().
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...