>>55667981well long story short i have a client-server webapp side-project, and for years at this point it's been using json to communicate. while human readable, json is very bandwidth-inefficient, so i've been working on a complete protocol overhaul. the protocol draft is complete now, and from my calculations it's gonna be using up to 9 times less bandwidth compared to what i have right now, which i think is a major improvement.
compare this:
>[{"m":"m","x":50.00,"y":50.00}]to this (in hex for readability):
>0A 88 13 88 1331 vs 5 bytes, over 6x save. this all adds up.