title: When should an object be used instead of a json object?
body: <p>I'm designing a program in java where </p>
  
  <ol>
  <li><p>A lot of objects are just bags of data and don't really require any non-static methods.</p></li>
  <li><p>I want to easily save and load objects from the hard drive.</p></li>
  <li><p>Some instances of objects will need one additional attribute which I might add or take away over time.</p></li>
  <li><p>If some objects do have an additional attribute then I will still treat them as exactly the same kind of object most of the time.</p></li>
  </ol>
  
  <p>It seems like a good solution to this would be to store these objects in JSON format at runtime and never actually define a dedicated object for them. Is there any reason that you would not want to do this? i.e. is there any reason it is bad practice to store objects in json format when it is just for convenience?</p>