I agree with the clear coding style. Even if the compiler does generate a few more instructions, I would sacrifice a fraction of performance for code maintainability, clearity, and portability. On a typical workstation where interactive programs dominate, cpu utilization is so low that even if your applications runs a little slower it won't matter. The computer is waiting for user's input most of the time anyways. On servers, such performance loss can be compensated by the fact that next year's computer will always run faster.
1. I wonder how long it would take the animal-rights group to start protesting outside their company parking lot.
2. The initial investment and maintenance costs still seems high, but further integration efforts might change the picture
Don't overlook the potential of these 400MHz chips. Mind you that the fastest computer today (IBM Blue/Gene) is made from 30,000 700Mhz cores. Of course they got heck lot of I/O capabilities.
Slashdot Mirror
I agree with the clear coding style. Even if the compiler does generate a few more instructions, I would sacrifice a fraction of performance for code maintainability, clearity, and portability. On a typical workstation where interactive programs dominate, cpu utilization is so low that even if your applications runs a little slower it won't matter. The computer is waiting for user's input most of the time anyways. On servers, such performance loss can be compensated by the fact that next year's computer will always run faster.
1. I wonder how long it would take the animal-rights group to start protesting outside their company parking lot. 2. The initial investment and maintenance costs still seems high, but further integration efforts might change the picture
Don't overlook the potential of these 400MHz chips. Mind you that the fastest computer today (IBM Blue/Gene) is made from 30,000 700Mhz cores. Of course they got heck lot of I/O capabilities.