anchor.diff:  
   *Why this section havs things from the Cons section but consider differrently?*
   
  -```
  +
   In Cons section descible problem should be concerned, likely to be done wrong, or the limit of the design they can be solve in implementations or not is not important!
  -```
  -
  -```
  +
  +
  +
   Known issue is the problem persist in even the well designed; or persist due to the underlying infrastructure, application, programming language, etc!!
  -```
  +
   
   
   ==== Communication:
   
   Happen in non pure data solution, when Components don’t function independently of each other. Some means of communication is necessary
  -• Two approaches (both viable):
  -
  -```
  -– Direct communication using dynamic cast and function calls
  -– Indirect communication using message passing
  -```
  +
  +* Two approaches (both viable):
  +** Direct communication using dynamic cast and function calls
  +** Indirect communication using message passing
   
   In pure data solution, by not query or just loop through interested component at one update cycle, the Processor eases out the need of other communication, but in complex scenario, such as combine with outter event handling such as Network, where message passing is nature, the problem still persist!
   
  
positive.code: 
  === System ~ Processor?
  
  ```
    In a pure ES, this is not a thing, really. Some implementations force this on you because they couldn’t think how to do the ES job efficiently… but it’s still not a thing. All of your code that isn’t an ES is a "`system`", technically.
  ```
  
  System = everything that isn’t an Entity or a Component but uses Entities and Components.
  
  
negative.code: Read: link:http://blog.gemserk.com/2011/11/13/scripting-with-artemis/[http://blog.gemserk.com/2011/11/13/scripting-with-artemis/]
  
  Nearly one end up back to half ass solution, not a pure data ES if their really need scripting in.
  
  
  ==== Arbitrary Routine and Query
  