Can you give a compelling reason to change that?Yeah, because correctness is better than speed. I am willing to wait 2 milliseconds longer for an image to show up if it means I can open untrusted images without having my machine taken over. (See recent libpng and vorbis buffer overflows in Firefox.)
Remember, higher-level languages are almost as fast as C. For some languages, that "almost" is less than 2x slower.
Software becomes twice as slow every two years.
And it becomes 10x less correct. Less speed for less bugs is a reasonable tradeoff, considering computers double in speed every few years. You can buy speed at newegg for $100, but you can't buy correctness anywhere. No program I use today is particularly slow, but many are horribly incorrect.
So it seems like optimizing for speed is a bad idea. Programs that get me the wrong answer quickly are worthless.
Oh, but you don't write incorrect or unsafe C code... only other people do... I get it...