~/talk

Async and Streaming JS - Are we doing it wrong?

Talkat JSConf EU 2014 · 2014-09-13..09-14· [javascript, nodejs, frontend-architecture]
slides:none on file

Promises become the default but cancellation not in ES6 promises creates real wasted work for autocomplete and long IO. Reactive Extensions show observables can implement mouse drag and autocomplete with linear code using flatMap takeUntil and debounce for autocomplete and handle polling and out‑of‑order responses. Node stream revisions and WHATWG streams aim to fix low‑level IO while reactive streams add backpressure via request N and pauseable buffer semantics. Async/await and proposed async generators promise simpler syntax without losing composability.

AI-written summary · about

  1. 0:00Introduction
  2. 3:10Quotes
  3. 7:35asynchronous programming landscape
  4. 9:43promises
  5. 15:10autocomplete
  6. 16:58FRP
  7. 17:31Generators
  8. 18:20Async await
  9. 19:09Stream processing
  10. 21:06Darts
  11. 21:36Reactive streams
  12. 22:14Observables
  13. 22:52Wrapup
~/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.