The problem with JSON and XML based file formats is the tendency to require further parsing to decode values from strings. A universal interchange file format would have the ability to express all common data types through the composition of atomic values and containers.
-
Show this thread
-
Between all the major programming language families, you won’t find more than a couple dozen atomic types, a dozen distinct (up to isomorphism) container types, and a couple conventions for nominal containers that achieve globally unambiguous name scoping.
4 replies 3 retweets 37 likesShow this thread -
A desirable property here is: A value expressed in a universal interchange format unambiguously expresses its type, with no question of e.g. whether a string should be interpreted as a string, an enum, or a hex encoded byte array.
9 replies 1 retweet 42 likesShow this thread -
Another desirable property is diffability. JSON makes single-line semantic changes require multi-line adjustment of commas, and XML with end tags.
8 replies 0 retweets 31 likesShow this thread -
Finally, real data contains some equivalent of pointers or references, often with cycles. A universal interchange format must be able to express a snapshot of this data at a point in time, including references to external data that may be found elsewhere.
9 replies 2 retweets 44 likesShow this thread -
It’s the lack of this notion of local and remote references in data that leaves Java and C# requiring ad hoc database glue layers in languages that were otherwise sufficiently high-level that they could have solved the problem in a wonderfully general way.
25 replies 0 retweets 40 likesShow this thread
Please share your player support ticket number and I’ll make sure the team looks into it.
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.