go-json

There's various alternatives. For example: - https://github.com/goccy/go-json - https://github.com/bytedance/sonic

Someone made a benchmark of serialization libraries in go [1], and I was surprised to see gobs is one of the slowest ones, specially for decoding. I suspect part of the reason is that the API doesn't not allow reusing decoders [2]. From my explorations it seems like both JSON [3], message-pack [4] and CBOR [5] are better alternatives. By the way, in Go there are a like a million JSON encoders because a lot of things in the std library are not really coded for maximum performance but more for easy of usage, it seems. Perhaps this is the right balance for certain things (ex: the http library, see [6]). There are also a bunch of libraries that allow you to modify a JSON file "in place", without having to fully deserialize into structs (ex: GJSON/SJSON [7] [8]). This sounds very convenient and more efficient that fully de/serializing if we ju

https://github.com/sugawarayuuta/benchmark - Performance looks pretty comparable to go-json (https://github.com/goccy/go-json). Faster in some tests, slower in others. Not sure if it'd be worth switching for me. Good work either way. Would be interested to see benchmarks of the latest version.

I find the circles, crosses and triangles on https://github.com/goccy/go-json#json-library-comparison hard to comprehend. I guess that circle means "yes", cross is "no" and triangle is "partial" or something. However that is really just based on context. (I guessed the symbols from what I thought the data should be) I would suggest using words like "yes", "no" and "partial". They are short and clear. If you really want to do symbols I recommend using for yes, and still spelling out whatever triangle is supposed to mean.

Hi mate, very interesting library. Keep it up. Improvement suggestion: While reading the README, the JSON library comparison [1] it's confusing, at least to me. It uses symbols like: ○, and △ which are not obvious. I would rather use "yes/no" or the classic check/x (unicode chars, HN does not support them here) if you want to use symbols. I don't know what "△" even means, so I cannot suggest an alternative. Just my 2 cents. [1]: https://github.com/goccy/go-json#json-library-comparison Edit: This 2021 I have the objective to contribute more to OS projects. Is it OKay if I submit a PR with the change? Thanks!

I develop a super fast JSON library ( https://github.com/goccy/go-json ) . It is drop-in replacement of encoding/json. This library is available by simply replacing the import statement. It's more compatible and much faster than json-iterator/go. Please give me your feedback ! Thanks !