Don't optimize, write optimal by Davit Abgaryan (Arm) | JSConfAM19
summary
Claims that pragmatic code structure yields speed: prefer predictable control flow and naming over microbench tweaks; avoid negative conditionals and don't repeat yourself inside to keep JITs happy. Demonstrates concrete pitfalls — nested helpers, deleted properties and changing object shape — and shows that preserving shape and property order matters for hidden-class optimizations. Shows an application refactor that measurably speeds execution, with live demos and numbers comparing before/after. Emphasis on patterns not tools.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:53Performance optimization example
- 2:42Readability issue
- 3:41Always don't avoid negative conditionals
- 4:32Method Chaining
- 12:03Avoid nested functions
- 13:02Write shorter functions
- 14:00Hidden classes
related talks
58mImproving Quality of JavaScript Code
01h 03mFunctional Programming in JavaScript
33mJavaScript: The V8 Engine optimization tips (...)
46mInvisible performance. How fast is your JavaScript code?
29mExtreme JavaScript Performance
56mThe Better Parts
23mA sneak peek into super optimized code in JS frameworks
01h 01mRediscovering JavaScript