~/talk

Invisible performance. How fast is your JavaScript code?

TalkinSpanishat Codemotion Madrid 2015 · 2015-11-27..11-28· [javascript, web-performance]
links:none on file
slides:none on file

Covers practical JavaScript performance tips: use 'use strict' and a linter (Standard) to catch bad patterns, prefer high-level constructs like Object maps and Object.assign instead of long if/else chains, and use LRU caches to avoid repeated expensive work (e.g., regex or distance calculations). Recommends factory/composition instead of new/constructors to reduce prototype/memory issues, avoid heavy regexes when simple string checks suffice, and prefer native methods and block-scoped let/const over var for more predictable performance.

AI-written summary · about

  1. 0:00Introduction
  2. 7:19Use 'use strict'
  3. 15:25Avoid 'else' and 'switch' with objects
  4. 18:12Cache frequent results
  5. 21:25Use native JS methods
  6. 24:54Declare with 'let' and 'const'
  7. 26:42RegEx: when and how
  8. 31:11Avoid unnecessary 'bind'
  9. 33:41Constructor alternatives
  10. 43:17Simplicity for performance
  11. 44:21Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.