anchor.diff:  = terms
  -:author: 
  -:revnumber: 
  +:author:
  +:revnumber:
   :revdate: 2016/03/17 20:48
   :relfileprefix: ../../../
   :imagesdir: ../../..
  
positive.code: 
  link:http://en.wikipedia.org/wiki/Object-oriented_programming[http://en.wikipedia.org/wiki/Object-oriented_programming]
  
  —————————————————————————————
  
  
  == Data Oriented Programming
  
  [This just not exist]
  
  If you use Data-oriented_languages, you can call it Data Oriented Programming! You may talking about *Data Oriented Design (Architecture)* instead
  
  
negative.code:   Data oriented design is an approach that extracts the operations on the data from the “objects” and flattens the things that they need to run in order to be cache friendly. According to the literature (I got my first exposure in Game Engine Gems 2, Chapter 15), in many cases it actually simplifies the code.
  ....
  
  From atomix ‘s overview:
  
  Data oriented architecture is focus in Data arrangement and process(delay of data and the dataflow) and everything is Data, with a repository! It have more aspects than Data driven architecture and not talking about “the force of generative data”.
  
  In hardware level, data oriented appear in structure and operations of chip set, when input and output are carefullly design to get batch/cache efficient.
  