2 ms·
You should make the connection of QTT and QSN to Rust more clear by coming up with a backronym for RSON.
by earthboundkid 4y ago
You should make the connection of QTT and QSN to Rust more clear by coming up with a backronym for RSON.
- chubot 4y agoHm I wasn't aware of RSON. https://github.com/rson-rs/rson https://github.com/rson-rs/rson QSN isn't intended to be tied to Rust in any way (and isn't), while RSON says it uses the Serde data model. This gets at an issue I have been having a hard time explaining, mentioned here: http://www.oilshell.org/blog/2022/03/backlog-arch.html http://www.oilshell.org/blog/2022/03/backlog-arch.html That is, narrow waists are necessarily a COMPROMISE. JSON is a compromise, and Rust users will be equally unhappy as Lua or Erlang users. That is a feature and not a bug for something meant of interoperability. You are "stuck with" the lowest common denominator, but that's what enables interop. (The lowest common denominator of them all is Unix byte streams.) I contrast "monoglot" serialization formats like Python pickle an Go .gob with language-independent formats like JSON, TSV, and HTML. The wisdom of JSON is that Crockford specified it independently of JavaScript. But both are useful. It's not clear if RSON is meant to be monoglot or polyglot, but it's a huge difference and it seems more monoglot. QSN on the other hand is definitely a polyglot design like JSON, despite being derived from Rust.