Re: [Json] JSON and int64s - any change in current best practice since I-JSON

[Rob Sayre <[e-mail]>]

On Wed, Jan 17, 2024 at 9:23 AM Carsten Bormann <[e-mail]> wrote:

>
> > - if they are allowed, are they expected to have (somewhat unspecified)
> JSON behavior, or are they expected to behave in int-like fashion?
>
> There is no JSON behavior.  They are numbers, "similar to that used in
> most programming languages”.
>

Yes, and many JSON implementations work just fine with arbitrary precision
numbers, because that's what is used in the language.  In Ruby:

irb(main):002:0> require 'json'

=> true

irb(main):004:0>
JSON.parse("12341234124123412431234123412340982133049812394")
=> 12341234124123412431234123412340982133049812394

I think we all have things to dislike about JSON, but one thing that's hard
to argue with is its adoption. It was just "eval" in JavaScript as well as
Python at first, so that took off right away.

Similar to the JavaScript Number type:

> 123 + "abc"
'123abc'

So, then people begin to dislike the "keep going no matter what" style of
these approaches, because they do generate bugs in programs that are more
critical than MySpace pages. Then you get things like I-JSON, which
describes what not to assume about JSON in Ruby, for example.

thanks,
Rob