Should You Favor Performance or Readability?
summary
Examines the trade-off between code readability and runtime performance using JavaScript experiments and measurements rather than opinion. Compares tools like ESLint/Prettier, React Profiler, DevTools Core Web Vitals and a custom benchmark (JSBench + an AI layer) to evaluate examples; reports a team survey on cloning methods showing concat is fastest while structuredClone is the most readable but slowest, and quantifies impact (e.g., 1 ms saved per call → ~15 minutes CPU per million runs).
AI-written summary · about
chapters (5)
related talks
34mYou should use [insert library/framework], it's the bestestest!
41mMake JavaScript Faster
58mImproving Quality of JavaScript Code
27mDoing the Least Amount of Work: An Intro to Runtime
58mImproving the Quality of JavaScript Code
22mWhy Performance Matters - JSConf Budapest 201
24mThe missing guide for deciding between 3rd party library and custom code -JSWORLD 2023
33mDemystifying Web Performance Tooling