title: Considerations about a simulation game
body: <p>The kind of simulation game that I have in mind is the kind where you have things to build in various locations and workers/transporters that connect such locations.</p>
  
  <p>Something more like the Settlers series.</p>
  
  <p>Let's assume I don't want any graphics at the moment, <strong>that</strong> I think I can manage.</p>
  
  <p>So my doubts are the following:</p>
  
  <ol>
  <li>Should every entity be a class and each one have a thread?</li>
  <li>Should entities be grouped in lists inside classes and each one have a thread?</li>
  </ol>
  
  <p>If one takes implementation 1, it's going to be very hard to run on low spec machines and does not scale well for large numbers.</p>
  
  <p>If one takes implementation 2, it's going to be better in terms of resources but then...</p>
  
  <p>How should I group the entities?</p>
  
  <ol>
  <li>Have a class for houses in general and have an Interface List to manage that?</li>
  <li>Have a class for specific groups of houses and have an Object List to manage that?</li>
  </ol>
  
  <p>and what about threads?</p>
  
  <ol>
  <li>Should I have the simplistic main game loop?</li>
  <li>Should I have a thread for each class group?</li>
  <li>How do workers/transporters fit in the picture?</li>
  </ol>