> To the point that I don't understand why it was left out of JSON Because JSON has generic numbers that just happen to be able to represent every numeric IEEE

> To the point that I don't understand why it was left out of JSON Because JSON has generic numbers that just happen to be able to represent every numeric IEEE floating point double value. In theory you could have an implementation that uses a BigDecimal class or something similar to represent numeric values. Which is of course completely incompatible with every other JSON implementation and just asks for badly tested edge cases to rear their ugly head.