4 ms·
Author here. As for 1.: CSV files are encoded as a stream, so they can be as large as needed. JSON is dumped as a whole from memory, I'd be keen to see if some
by pudo 13y ago
Author here.
As for 1.: CSV files are encoded as a stream, so they can be as large as needed. JSON is dumped as a whole from memory, I'd be keen to see if someone has written a streaming JSON encoder.
2.: Consuming, no. I normally load them in a browser with D3 or jQuery to feed them into a graphic or other interface.
3.: I'd argue this is out of scope for dataset, but simpler REST API makers would definietly be cool. Check https://github.com/okfn/webstore https://github.com/okfn/webstore - this is what dataset came out of, and it makes somewhat RESTish APIs.
- yesbabyyes 13y agoI'd be keen to see if someone has written a streaming JSON encoder. This looks interesting: https://gist.github.com/akaihola/1415730 https://gist.github.com/akaihola/1415730 Edit: dataset looks like a really interesting library!