You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume, there is the type saved in the []byte. When u store it as json, there is no type definition, its loose and will get duck typed while loading. I also assum this will make this implementation faster than a json encoding/decoding.
But thats just an assumption, i did not check the code, nor did i use it till now :D
When pasting the JSON below into the official message pack site, it shows a significant decrease in size
https://msgpack.org/index.html
{"bar":"spam","foo":[{"spam":"ss","size":{"w":320,"h":480},"n":10,"c":1},{"spam":"ss","size":{"w":300,"h":250},"n":5,"c":1},{"spam":"ss","size":{"w":320,"h":50},"n":1,"c":1},{"spam":"v","size":{"w":-1,"h":-1},"n":20}],"l":10,"b":1}
However when using this package it always shows that the generated output is larger than it's JSON counter part. Any reason why?
Is the site applying compression as well?
The text was updated successfully, but these errors were encountered: