GeneThomas

7 ms·

1. 61.▲
   by GeneThomas 2y ago

   The example you give is valid xᴇɴᴏɴ. The key and value may contain whitespace and must be delineated? <>s are that that made XML and HTML good.
2. 62.▲
   by GeneThomas 2y ago

   Both a C# and JavaScript implementations exist. The terse “single punctuation character”, e.g. <$> make it efficient to write, more efficient than JSON. There is no “extra open bracket”? There is a overview of how the indenting operat
3. 63.▲
   by GeneThomas 2y ago

   There is less typing than JSON.
4. 64.▲
   New better alterative to XML, JSON and YAML(xenondata.org)

   24 points by GeneThomas 2y ago|144 comments
5. 65.▲
   by GeneThomas 4y ago

   You are simply wrong about self synchronisation, simpler designs can not determine the code point boundaries from an arbitrary stream position. ᴜᴛꜰ-8 requires work to start decoding from near an arbitrary position. You purposely divulging m
6. 66.▲
   by GeneThomas 4y ago

   It is in that if one seeks to an arbitrary point in the stream one can find the start of the current code point. Code points always end with a 0 high bit. i.e. From any byte move back until one finds a byte with a high bit of 0, that is the
7. 67.▲
   Idea for Most Efficent Charset

   1 points by GeneThomas 4y ago|4 comments