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
-
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.
-
-
If performance demands it, you can later make MT improvements. The DoD design makes that an easy refactor in many cases.
-
As a final note: on days when my brain is deep in some other subject, *I* am bad at multithreading. Being able to tackle the actual problem at and and leave the MT for another day is a boon.
- 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.