Stéphane Épardaud

Oh, I didn't know it made it to RFC: https://tools.ietf.org/html/rfc7159 Its encoding section is interesting: 8.1. Character Encoding JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. The default...

> do you have any specific knowledge that the model is not JSON No, but since it was not made to be JSON (otherwise it'd use quotes) then I can...

It's also wrapped inside a `require.js` function which makes it impossible to parse as JSON as-is without interpreting the file, or using `require.js`.

So an online JSON validator says it's valid aside from the key quoting, which I suppose is a good news.

If we do, we're not low-level enough for higher-level libs to use this stuff and decide themselves what to do. If we don't, we're not high-level enough to be useful.

`Encoder` and `Decoder` are indeed asymmetric and I didn't like that at the time. They should both use buffers. In general, we should never use arrays for IO.

Well, not at all, it's a character buffer. Like an array of characters with position/limit. It allows you to transfer characters to and from anything, without having to allocate strings.

You're right. I did not finish it. It's a buffer for reading from a String ATM. It should be similar to a byte buffer, and optionally allow for reading from...

Well, obviously I've no time to finish it, and that's why I asked help from people who understand buffers. IO is a world in itself, and buffers seem to be...

ATM the `StringBuffer` is already more useful than a `String` because it allows you to read from a `String` in parts while pushing IO on the other end.