Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My favorite example is the meg's of commas and quotes that just aren't needed in memory.

Depending on the language and internal represenation, for any comma and quote not needed (which for a JSON document with, say, an object without nesting, is just 5 bytes per entry), you might get your strings doubled in size (because e.g. the language converted your fitting into 8bit utf-8 strings to its 16bit native string format), or have some huge constant boxing overhead (in say, Python), and several other fun things besides...



Right, is why I said strings can be a curve ball. But most of the data I see can avoid that fairly easily.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: