Crockford thought that you could avoid version impedance mismatches by not versioning things. This doesn't work! https://www.computer.org/csdl/mags/co/2012/04/mco2012040006.html …pic.twitter.com/tShrqyoR3G
-
The point of JSON is to map to the "native" types in each language. JSON's approach has drawbacks, but versioning is irrelevant.
If that's the point, the original spec is quite odd in specifying, multiple times, "very much like a C or Java". Why say that?
-
-
also odd that it says that it's based on of ECMA-262 and only has one type of number. Relatively few languages only have one number
-
IMO it seems more like someone who writes js created a thing that's convenient in js and falls over if you want (for ex) int and fp
-
if it were versioned like websockets someone could tell me in the protocol they're using extension XYZ and pass me an int
-
instead they tell me verbally that vars A, B, and C, which are passed as strings, should instead be parsed as ints
-
I want to use a serialization format to avoid having to do exactly that.
- 2 more replies
New conversation -
-
-
I think this means the _syntax_ of a C or Java number or string. Otherwise it makes no sense -- C and Java strings are not similar.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.