2 ms·
This definitely interests me as well. Another 'wasteful' mechanism is the nearly-ubiquitous use of JSON over a more optimized format like protocol buffers, etc
by jeffbarg 8y ago
This definitely interests me as well. Another 'wasteful' mechanism is the nearly-ubiquitous use of JSON over a more optimized format like protocol buffers, etc... It reminds me of another HN discussion here: https://news.ycombinator.com/item?id=9761667 https://news.ycombinator.com/item?id=9761667
I understand that economically the savings in development time usually outweighs the bandwidth costs, but I would be interested in any analysis on how wasteful this is overall.
- tatersolid 8y agoWe tested this at $dayjob and JSON+gzip wins hands down because you already have an optimized native-code parser in the browser. Large-ish arrays of similar JSON objects compress very well with gzip, and ultimately parse more quickly than JS-based protobuf or msgpack, at least in our testing.