Hacker News Reader

olsnon MsgPack vs. JSON: Cut your client-server exchange traffic by 50%

i understood your point, however the speed in the user's browser is not important since it's just 1 operation, whereas the server has to do most of the operations decoding/encoding all that

i guess there are pros and cons on both sides, certainly nice would be something like a native BSON implementation with extensions in the browser/debugger to make it readable

olsnon MsgPack vs. JSON: Cut your client-server exchange traffic by 50%

then you could get a c extension for MsgPack, that would have to parse less bytes than the JSON c extension and therefore be faster

JSON is very good, no doubt about that - but i think that even JSON can be optimized, does not have to be by MsgPack, but probably by a binary format.

olsnon MsgPack vs. JSON: Cut your client-server exchange traffic by 50%

do you have a specification or even some prototype on github? would be interesting to see

olsnon MsgPack vs. JSON: Cut your client-server exchange traffic by 50%

For the native JavaScript implementation you are correct - no doubt about that it is faster there, however, looking at the server-side it looks the other way around: for example parsing MsgPack in Ruby is about 5x faster than parsing JSON - you can rewrite your benchmark to Ruby and try for yourself