~/talk

Alois Reitbauer interviewed at Velocity 2012

Talkat Velocity US 2012 · 2012-06-25..06-27· [web-performance, java]
links:none on file
slides:none on file

Problems center on third‑party content like CDNs social widgets and ads and on measuring when users actually see content not just full load times. Browsers partially implement navigation timing while Safari and legacy browsers lack it so teams use polyfills and JavaScript hooks. Claims: resource timing data that native APIs promise in about 1–1.5 years can be approximated today, and JavaScript instrumentation (DOM hooks and framework-specific hooks) measures render and event execution times. A combined browser server and synthetic approach is required.

AI-written summary · about

  1. 0:00What are the primary user experience management problems
  2. 1:03Can you talk about legacy browsers
  3. 2:07What types of analysis are available today
  4. 3:45How do you see it playing out
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.