jsoniter VS GJSON

https://github.com/json-iterator/go an alternative JSON encoding package which allows to stream (flush out) encoded data as soon as it's able to (which is in contrast with the stock package which buffers everything until the encoding is known to be complete and OK).

What to use Easyjson is about the top of the pack and it's straightforward. The downside of efficient tools is that they use code generation to create the code required to turn your structs into json to minimise allocations. This is a manual build step which is annoying. Interestingly json-iterator also uses reflection but it's significantly faster. I suspect black magic.

jsoniter for low level access to JSON encode and decode

I think you have to parse the json, if you dont know exactly what you are looking for and want some validation und prevent manual parsing errors. For parsing big json files it is recommend to read and decode it as stream. Here is an example. If you have serious performance criteria take a look at jsoniter. It can be used as 1 to 1 replacement for standard library.

Takes like 10 minutes to write and parses very efficiently. https://github.com/json-iterator/go looks like it can provide such simple parsing

Need to compare with https://github.com/json-iterator/go too!

tidwall/gjson - JSON processing.

GJson

Reading and navigating arbitrary JSON: I've used https://github.com/tidwall/gjson, many others like https://github.com/buger/jsonparser are also out there.

Why is this considered a good pattern? Sure, I can see how one would make the argument for simplicity in that it's only a single file, however, it seems like it took an axe to usability and productivity in the process.

If your use case is more complex than "does this key exist", then there are several libraries out there that will be helpful. I've used and like gjson (https://github.com/tidwall/gjson) which has good handling of paths/queries.

I love https://github.com/tidwall/gjson and https://github.com/tidwall/sjson for fast and frictionless json reading and editing. It makes life so much easier for cases where you don't want to model a tree of nightmare-ish API responses, like Elasticsearch.

You can use gjson and access properties by JSON Path.

I would check out https://github.com/tidwall/gjson

Don't use structs in this case, use https://github.com/tidwall/gjson to directly query the json string.

gjson package could also be useful for this case (https://github.com/tidwall/gjson). Of course, it wouldn’t show the difference, but local json (I assume it’s a model data, used as a reference) can be used to get keys list and values to compare with.