undefined | Better HN

0 pointsearthboundkid4y ago0 comments

Make rows 1 dimensional. You don’t need the second dimension, it’s implied by header length. Once you do this, the JSON gzips down to about the same size as CSV, according to the last time I tested this IIRC.

0 comments

anonytrary4y ago

I edited-in the "2DArray" because I thought it was confusing... But you're right, just calculate offsets. The dominating term is still quadratic, and the term you mentioned is linear. It could be worth it for a scaled org like Google!

I wonder which parses faster. I guess CSV does but then the consuming code would still have to parse the strings into JS primitives...

earthboundkidOP4y ago

I haven't tested this, but my guess is that because the browser built in JSON.parse will be faster than whatever CSV parser you can write in JS just because it's precompiled to native code. Then the question becomes how long does it take to do the unpacking loop, but it should be pretty quick.

I'd love it if someone did a benchmark though.

dragonwriter4y ago

Heck, you could do a single 1-D list (no object), and just give the header count as the first element, which would be even more compact.

earthboundkidOP4y ago

Smart idea.

j / k navigate · click thread line to collapse

0 comments

anonytrary4y ago

I wonder which parses faster. I guess CSV does but then the consuming code would still have to parse the strings into JS primitives...

earthboundkidOP4y ago

I'd love it if someone did a benchmark though.

dragonwriter4y ago

Heck, you could do a single 1-D list (no object), and just give the header count as the first element, which would be even more compact.

earthboundkidOP4y ago

Smart idea.

j / k navigate · click thread line to collapse