Writing a blog post on Data Oriented Design. Any skeptics want to share their worries/criticisms? Looking to address some of the most common ones.
Näytä tämä ketju
-
Thank you for the explanation. The model looks to me like Cilk's model ( https://en.wikipedia.org/wiki/Cilk ) which i liked a lot, but ultimately failed. IMHO, in the end all that matters is if the part of the model that depends on certain programmer abilities, can be satisfied or not.
The underlying task system does have many similarities to Cilk. The Mana Engine itself is more about defining data dependencies and guaranteeing safe access to data.
-
-
The problem with manually defined data dependencies is that it is very easy for people to fall in either under- or over- definition of dependencies. If a dependency is omitted (which BTW can easily happen even in the over-definition case) then safety cannot be guaranteed.
-
The engine will not compile if you attempt to access a data type that you have not pre-declared access to. Safety is guaranteed.
Keskustelun loppu
Uusi keskustelu -
-
-
What is even worse is that the dependencies are a product of data modelling, and people are not very good in doing good data model designs as the effects of their designs will happen down the road. My advice in these things is to simplify and constraint the problem.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
So i would work in something simplistic and limited like a map-reduce model or for graph problems look in graph DB parallel processing models. These models impose heavy constraints to the programmers, forcing people towards simpler designs, but they provide performance and safety
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.