4 ms·
You can transport it to an architecture of different endianness without loss of information or metadata and a transformation at destination. There are importan
by samatman 3y ago
You can transport it to an architecture of different endianness without loss of information or metadata and a transformation at destination.
There are important ways in which it is, in fact, "just bytes".
- rusk 3y agoEndianness etc is a feature of the encoding. Most JSON implementations I’ve used require the raw bytes to first be decoded as such.
- samatman 3y agoNo, endianness is not a feature of UTF-8 encoding. There isn't a UTF-8LE and a UTF-8BE. That's because the codeunit is bytes. Forget "decoding", you have to parse JSON. But you don't have to figure out how it's encoded first. Because it's a byte format. You already know.
- rusk 3y agoThere isn’t a UTF-8LE/BE because it is implicitly BE for wide characters. Any byte in a WC sequence cannot meaningfully be interpreted (exc character class, page etc) without its companions, so not just bytes. There is an element of presentation that must happen before “mere bytes” are eligible for JSON