Generally JSON APIs allow multiple standard conventions for naming keys, the most common ones in my experience being the snake case and lower camel case. Go provides a bit of a struggle working with these because it uses the less common upper camel case. The work around for this is to augment each field in a struct with the corresponding tag, but that quickly becomes tedious.

My idea would be to allow the encoder/decoder, as well as the global marshaller/unmarshaller to be configured in choosing this standard. Some example code that would go into encoding/json:

type FieldStyle int

const (
    Default FieldStyle = iota
    SnakeCase
    CamelCase
)

Where Default is the current setting with UpperCamelCase. SnakeCase would be the snake_case and CamelCase would be the JavaScript standard camelCase.

Then we could augment the encoder/decoder (and perhaps a global function too) to work in a way similar to:

enc := json.NewEncoder(w).SetFieldStyle(json.CamelCase)
// etc

And so on. Thoughts?