Hacker News new | ask | show | jobs
by chrisbrandow 298 days ago
It reminds me also of the original head of development of the Safari browser talking about at least the early days of building the browser. They had a rule that no commit of code could cause the browser benchmarks to get slower. And apparently he was maniacal about the rule.

I don’t know if that’s a good or realistic rule for most projects, but I imagine for performant types of applications, that’s exactly what it takes to prevent eventual slowdown.

1 comments

That reminds me of Linus' attitude about breaking userspace for security fixes.