The way to make a program faster is to never let it get slower.

I don't understand how you can improve performance continuously while adding features, unless you optimize parts of the program unrelated to the new features...

<i>Common excuses people give when they regress performance are, "But the new way is cleaner!" or "The new way is more correct." We don't care.</i><p>It's worth pointing out that increasing CPU speed will always make your software faster, but it will never make it more correct. Considering all of the WebKit browsers I've used seem to crash every half-hour, I think the WebKit team may want to rethink their software engineering strategy. Getting the wrong answer really fast is pretty much useless.

If you want some more insight into how the team works, this is a very good post as well: <a href="http://webkit.org/blog/174/scenes-from-an-acid-test/" rel="nofollow">http://webkit.org/blog/174/scenes-from-an-acid-test/</a>

You wonder what they do when a security fix slows Webkit down.