Most hazardous performance bottleneck misconceptions
Posted
by David Murdoch
on Stack Overflow
See other posts from Stack Overflow
or by David Murdoch
Published on 2010-04-20T22:36:57Z
Indexed on
2010/04/20
22:43 UTC
Read the original article
Hit count: 334
The guys who wrote Bespin (cloud-based canvas-based code editor [and more]) recently spoke about how they re-factored and optimize a portion of the Bespin code because of a misconception that JavaScript was slow. It turned out that when all was said and done, their optimization produced no significant improvements.
I'm sure many of us go out of our way to write "optimized" code based on misconceptions similar to that of the Bespin team.
What are some common performance bottleneck misconceptions developers commonly subscribe to?
© Stack Overflow or respective owner