Hector Martin

You do not understand floating point numbers. 2^53 is not the largest integer that can be represented accurately in 64-bit floats. *All* the integers *from zero to 2^53* can be represented, but *many more larger than that* can too. Just not all of them.

just read the URL i linked, it explains things very well

or... i dunno, argue with brendanhttps://twitter.com/brendaneich/status/526826278377099264?lang=en …

Yes, the URL you linked explains it: beyond 53 bits, you can only represent every 2 integers (and then every 4, then every 8, etc). But *you can still represent those integers*. The integer I'm using as an example is one such integer you *can* represent. Read it yourself again.

yeah, you can, and you can also get rounding errors based entirely on the engine... you can't do that in production, so most don't consider it an option

No, you cannot get "rounding errors based on the engine". IEEE 754 is *precisely* defined. The *same* integers are, or aren't, representable in *every single system using IEEE 754". The only problem here is toString rounds some integers to impossible ones for no reason.

you think every implementation follows the spec properly? this is web browsers; today doesn't apply to last decade, where the constraints existed

IEEE 754 predates web browsers. It came out in 1985. And besides, IEEE 754 is baked into CPUs anyway, so browsers aren't going to randomly mess it up. The only problem here is JS *lies* when converting to a string.