jsonparser VS jid

In this article, I will introduce you to a new package called astjson that I have been working on for the last couple of weeks. It is a Go package that allows you to transform and merge JSON objects with unmatched speed. It is based on the jsonparser package by buger aka Leonid Bugaev and extends it with the ability to transform and merge JSON objects at unparalleled performance.

Use this to extract the data value, and handle/unmarshal it accordingly.

jsonparser can decode, but can't encode

Best I've found is this: https://github.com/buger/jsonparser

I was actually just trying to get it into a []byte to use this package which claims it works well for unknown data structures.

`jj` is a little tool I wrote that uses https://github.com/buger/jsonparser

If you don't know the schema or you only need to access one or two fields in a much larger JSON object, I would recommend https://github.com/buger/jsonparser as it provides an easy API to access specific values without fully unmarshaling. This is an unusual use case though, 9 times out of 10 I would tend to use easyjson.

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.

It took me a while to grok jq, but now that I do I kinda like it? I don't think I want to learn yet another thing.

I do like tools that complement/supplement jq though, like jid: https://github.com/simeji/jid

Link for the lazy: https://github.com/simeji/jid

If you're trying to work out the structure and content of an API's JSON responses, you can keep paging through the documentation and the paged output of less or you can reach for more precise JSON parsing tools such as, jq and jid.

Yeah, I love me some jq, and my first reaction to the JSON tools page was 'What do these bring to the table that jq doesn't?". Gron and Jid changed my mind.