Once upon a time I had a 1ghz laptop it came with winXP and ran nice and fast (XP had not long been out and 1ghz for a laptop was quite good!) after a number of years and a number of updates the laptop crawled, was sluggish and not nice to use.
I reinstalled XP, woohoo nice and fast, then after 6-8 reboots I had updated XP, and no surprise it was back to its sluggish ways. I stopped using it for a while, thinking it "obsolete"
Then I decided to teach my girlfriend about CMS like she been asking, I know I'll wipe that laptop an put a different operating system on it.
What joy my laptop sprang back to a modest speed and became usable useful tool.
So while I agree that shaving the odd clock cycle per vbl is basically pointless, you *do* need to keep a weather eye on bloat.
The difference between a list and array or a bank is largely immaterial, methodology is important.
Sometimes "fastest" can mean time to market too...
(do you really have 2 weeks to waste to shave off those few clock cycles per frame)
I reinstalled XP, woohoo nice and fast, then after 6-8 reboots I had updated XP, and no surprise it was back to its sluggish ways. I stopped using it for a while, thinking it "obsolete"
Then I decided to teach my girlfriend about CMS like she been asking, I know I'll wipe that laptop an put a different operating system on it.
What joy my laptop sprang back to a modest speed and became usable useful tool.
So while I agree that shaving the odd clock cycle per vbl is basically pointless, you *do* need to keep a weather eye on bloat.
The difference between a list and array or a bank is largely immaterial, methodology is important.
Sometimes "fastest" can mean time to market too...
(do you really have 2 weeks to waste to shave off those few clock cycles per frame)