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
-
To be a devil's advocate... "some developers don't understand multithreading, and [with this system] they don't have to" - sounds just like the reasoning that lead to introduction of garbage collection. Not saying DoD is inherently bad. Just that such a goal is questionable.
Nothing wrong with garbage collection as long as it’s done “right” according to your needs and purposes. In a way, garbage collection is also in Mana in several ways. The Gfx API does “GC” to frame data when it’s done being used.
-
-
But I think you’re right to be skeptical. I have another post later on illustrating why it’s useful. You can implement something “single threaded” and then if you need to, make MT improvements later.
-
This reflects the realities of development. You often work on a team, where each member has different skills. Initial implementation of a feature can be “single threaded”, where safety is guaranteed and concurrent work will still be scheduled.
- Näytä vastaukset
Uusi keskustelu -
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.