title: JSON and dealing with unexported fields
body: <p>Is there a technical reason why unexported fields are not included by encoding/json? If not and it is an arbitrary decision could there be an additional back door option (say '+') to include even though unexported?</p>
  
  <p>Requiring client code to export to get this functionality feels unfortunate, especially if lower case is providing encapsulation or the decision to marshal structures comes much later than design of them.</p>
  
  <p>How are people dealing with this? Just export everything?</p>
  
  <p>Also, doesn't exporting field names make it difficult to follow suggested idioms. I think if a struct X has field Y, you can not have an accessor method Y(). If you want to provide interface access to Y you have to come up with a new name for the getter and no matter what you'll get something un-idiomatic according to <a href="http://golang.org/doc/effective_go.html#Getters" rel="noreferrer">http://golang.org/doc/effective_go.html#Getters</a></p>