GeneThomas

7 ms·

31.
by GeneThomas 2y ago
I am futureproofing.
32.
by GeneThomas 2y ago
TER is irrelevant. The Internet has shown the advantages of text formats at the high level, e.g. email and the web.
33.
by GeneThomas 2y ago
Make a point
34.
by GeneThomas 2y ago
https://news.ycombinator.com/item?id=42038004#42038525
35.
by GeneThomas 2y ago
See https://news.ycombinator.com/item?id=42038004#42049033
36.
by GeneThomas 2y ago
Is canonilization not irrelevant. Any format with comments is not canonical; so xᴍʟ is not, ᴊꜱᴏɴ has escapes options for string characters so it not either. Response to graph conjecture stated https://news.ycombinator.com/i
37.
by GeneThomas 2y ago
You misunderstand. Given that data MAY be a graph structure, the markup MUST support that. A tree with pointers to the parent nodes has a graph structure, a common enough occurrence.
38.
by GeneThomas 2y ago
I mean it can be encoded inline, including using \n in strings
39.
by GeneThomas 2y ago
See https://news.ycombinator.com/item?id=42049033 As terse as ᴊꜱᴏɴ.
40.
by GeneThomas 2y ago
Good.
41.
by GeneThomas 2y ago
> Again, how is this different from `xml:id` It is a tidier solution. > I still can't get what makes timestamps (and GUIDs) so special so that they have special sections in your document. They are common in data. > [...] bool
42.
by GeneThomas 2y ago
See https://news.ycombinator.com/item?id=42056666
43.
by GeneThomas 2y ago
I shall elaborate on the first paragraph of the web page: • Terse. Xᴇɴᴏɴ is as terse as ᴊꜱᴏɴ using 3 characters per scalar value <key=value> rather than ”key”:value, (4) or ”key”:”value”, (6). Xᴇɴᴏɴ is significantly more terse than xᴍ
44.
by GeneThomas 2y ago
I don’t love this. > I can't see how different is that comparing to XML or JSON that semantically "have graph support" just because they also can declare something considered ids and references to the identified element. W
45.
by GeneThomas 2y ago
> why did you use comma instead of other characters for grouping? Because English is the global lingua franca > I like to hear why then Unlike Unicode xᴇɴᴏɴ must be defined in one grammar. Having special names, like $type, and hoping
46.
by GeneThomas 2y ago
A basic scalar pair in ᴊꜱᴏɴ is "key":"value", or "key":value, so a 4 or 6 character overhead. xᴇɴᴏɴ is <key=value>, 3 characters. In my tests xᴇɴᴏɴ IS more terse.
47.
by GeneThomas 2y ago
> `<<$>` but not `<$>>` Having both begin and terminate arrays start with << is more consistent. > `<>` and `<&>` (`{` and `}`?). Using `{` and `}` would lead to more special characters. > Au
48.
by GeneThomas 2y ago
There exists a charset that is more efficient than UTF-8.
49.
by GeneThomas 2y ago
It IS more terse than ᴊꜱᴏɴ and xᴍʟ and has many compelling features.
50.
by GeneThomas 2y ago
JSON has superfluous quotes for the field names in objects, so overall xᴇɴᴏɴ is more terse than ᴊꜱᴏɴ.
51.
by GeneThomas 2y ago
That is hard to believe, the data being serialized may always have a graph structure.
52.
by GeneThomas 2y ago
Indentation in xᴇɴᴏɴ is optional and for readability.
53.
by GeneThomas 2y ago
It is more terse than JSON.
54.
by GeneThomas 2y ago
>But that doesn't really justify the use of comma in numbers. Readability. >I was asking why that particular variant [of Base64] was used. I repeat, we are using the ʀꜰᴄ 4648 variant. > [separate standards documents] do you th
55.
by GeneThomas 2y ago
> Consider the approach taken by XML 1.1 I evaluated xᴍʟ 1.0 and 1.1’s restrictions but consider the alternative, accepting anything but the empty string to be simpler. >A lot of English-speaking countries actually have `.` and `,` sw
56.
by GeneThomas 2y ago
- The flexibility in name is to support the plethora of programming languages. - Commas are for readability as per English. - Three digits are recommended for the encoder. - Textual data is decoded into binary information in software so set
57.
by GeneThomas 2y ago
See the opening paragraph.
58.
by GeneThomas 2y ago
It has ALL of the advantages of xᴍʟ.
59.
by GeneThomas 2y ago
Grudgingly ha ha. As per https://xenondata.org Xᴇɴᴏɴ is more terse than even ᴊꜱᴏɴ and has the advantages listed in first paragraph.
60.
by GeneThomas 2y ago
The “readable indented text” refers to https://xenondata.org/#scalars where multiple lines of text can be indented and extracted as expected. One can argue that JSON is not readable due to requiring escaping (\n) for multip

More ›