rson
ssv
| rson | ssv | |
|---|---|---|
| 1 | 1 | |
| 21 | 4 | |
| - | - | |
| 0.0 | 3.9 | |
| about 3 years ago | about 2 years ago | |
| Rust | Python | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rson
-
Why isn’t there a decent file format for tabular data?
Hm I wasn't aware of 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
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.
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.
ssv
-
Why isn’t there a decent file format for tabular data?
https://github.com/tmccombs/ssv
So far it's just a python library, but I'm planning on adding editor plugins at least for vim, vscode and maybe emacs, libraries for additional languages, and maybe some cli commands for it.
One distinction from the OP is the delimiters also include a tab (for fields) or newline (for records) by default (but not in "compact" mode). That has the benefit that the files are at least readable with editors and pagers that aren't aware of the format.
What are some alternatives?
hsv5 - HTML5 Based Alternative to CSV, TSV, JSONL, etc
odiff - The fastest pixel-by-pixel image visual difference tool in the world.
parquet-wasm - Rust-based WebAssembly bindings to read and write Apache Parquet data
TileDB - The Universal Storage Engine
ndjson-spec - Specification
AwesomeCSV - 🕶️A curated list of awesome tools for dealing with CSV.