> This project's idea is to give stright numbers for some definitely bad > coding practices (e.g. map() in the void context), and things which vary > a lot depending on the context, but are interesting to think about (e.g. > the last example of caching the result of ref() or a method call)
I think this would be handy. I spend a fair bit of time wondering/testing myself. Would be nice to have a repository of the tradeoffs. OTOH, I spend too much time mulling over unimportant performance optimizations. The foreach/map comparison is a good example of this. It only starts to matter (read milliseconds) at the +100KB and up range, I find. If a site is returning 100KB pages for typical responses, it has a problem at a completely different level than map vs foreach. Rob "Pre-optimization is the root of all evil" -- C.A.R. Hoare
