#Tech Ramblings of Amasawa's Game Engine
11 messages · Page 1 of 1 (latest)
@next field somewhere for your toughts
Sometimes that's not possible, but even in the case where one archetype really wants the data of another archetype being processed by another thread, there are ways to expose weak refs to those without exposing the entire data (and hence be more open to data races and sync issues)
I think you'll find a lot of devs, espically indie, are going in without a plan. You're talking about some actual product engineering that is skipped 9/10 times.
Sure, and their approach makes sense given their constraints and some other variables. I simply care because I can't stand without knowing the deep ends of everything, which is already flawed, but due to the asperger spectrum, I can't do better.
i mean, you'll need to back out of that mindset
does the master carpenter care about the underlying physics of the hammer, yes. Do the care about the manufacturing process of the hammer and the materials? naw. ain't got time for that.
Sometimes good enough if perfect.
Yeah, probably.
I'm unoptimized, but it is what it is.
I find those topics interesting regardless, so I also have a lot of fun with the process.
Optimized yourself first