3 ms·
Maybe you can't blame the quote author but the quote itself is definitely a problem now. In my experience it is mostly used as an excuse not to think about per
by IshKebab 4y ago
Maybe you can't blame the quote author but the quote itself is definitely a problem now.
In my experience it is mostly used as an excuse not to think about performance at all. "The quote says we can worry about it later!"
That's why the quote needs to die.
- kaba0 4y agoOr extended with the context, like “Yet we should not pass up our opportunities in that critical [hot loop]”
- kllrnohj 4y agoThe "hot loop" is also a myth. Very few programs actually have a hot loop with larger-than-average returns on optimizations. Heck, the blog post itself is an example of that not being the case - it's startup that's slow, not the program's steady state hot loop. For something you actually spend a significant amount of time using continuously, yeah maybe it has a hot loop. But even then, probably more like hundreds or thousands of hot loops depending on the features being used, what stage the program is in (eg, blender while editing the scene is very very different from blender while exporting a rendering).