3 ms·
The point I am ultimately trying to make is that, in many cases, the reason to avoid multi-threading is because it's not actually the fastest way to do somethin
by bob1029 5y ago
The point I am ultimately trying to make is that, in many cases, the reason to avoid multi-threading is because it's not actually the fastest way to do something. It's that simple.
The implicit concern (if you could not infer from the content of my link above) being that the developer community is completely blind to the performance capabilities of a single computer/core/thread in 2022 and are inclined to automatically skip over these simple solutions in favor of a multi-threaded solution.
- spacemanmatt 5y agoI feel like that is a point that doesn't need making because it's sorta elementary that task switching is expensive and avoidable in some cases. Especially when the explicit context is indie development, not squeezing some performance out of the threading model at large scale.