Three JavaScript performance fundamentals that make Bluebird fast
Interesting article now take these suggestions and toss them out the window. Architecture, correctness, maintainability and readability of code are much more important than optimizing for these extreme edge cases.<p>If there are performance issues, profile and refactor only the affected areas. Most of the time your code isn&#x27;t going to get exercised enough to make any difference. You&#x27;re also fighting JIT assumptions, since all VM devs will attempt to optimize against common patterns - so though these performance &#x27;bottlenecks&#x27; may be true today, that may not be the case tomorrow.<p>Anectode: I had a co-op student preemptively apologize for using a double for-loop brute force search as non-optimal and not &#x27;clean&#x27;, during his code-review. The lists in question were guaranteed to have a size of 5, and that code was executed once per life-time of the app.