3 ms·
It is a relative term. I use it here because most introductory posts about encoding/decoding in go (like https://blog.golang.org/json-and-go https://blog.golan
by joncalhoun 10y ago
It is a relative term.
I use it here because most introductory posts about encoding/decoding in go (like https://blog.golang.org/json-and-go https://blog.golang.org/json-and-go) don't touch on these at all. Instead many people figure each of these out separately over time.
- laumars 10y agoI'm inclined to agree with the grandparent here. It's good that you're willing to contribute to the already impressive catalogue of Go reference material but your guide is really more of an introduction into the JSON marshaller than advanced techniques about encoding and decoding in the more general sense. Sadly I do feel a little mislead by the title since I was hoping for something a little more challenging than JSON - though had I known it was just JSON I certainly wouldn't have opened the page so maybe the title works? ;) On a positive note, it does look like it's well written. Detailed with clear examples and laid out in a clean design that's easy to follow.