~/talk

Design decisions in React-based ClojureScript applications

Talkat :clojureD 2017 · on Saturday, 2017-02-25· [react, frontend-architecture]
links:none on file
slides:none on file

Team builds about five React ClojureScript SPAs and reports practical tradeoffs: prefer one big app-state atom, keep components dumb and send events into a channel-based dispatcher (the big loop), or use Om Next style co-located queries when data needs are highly dynamic. For expensive recomputations pick dataflow/derived atoms (Re-frame/Reagent); for syncing send backend responses back through the event loop and bundle updates with a follow-up query. Resolve conflicts with optimistic versioning or full locks depending on conflict likelihood.

AI-written summary · about

  1. 0:00Start
  2. 1:16Recap on the Programming Model of React
  3. 2:55Organizational State
  4. 4:18Structural Mismatches
  5. 4:50Unpredictable Data Needs
  6. 5:30Updating Your State
  7. 6:59Guiding Rules
  8. 9:08The Big Loop
  9. 10:37Co-Located Queries
  10. 13:35Dataflow Programming
  11. 17:30State Synchronization of the Remote Back-End
  12. 21:33Pessimistic and Optimistic Concurrency Control
  13. 22:29Pessimistic Concurrency Control
  14. 24:34Advices
  15. 25:03Do You Need Expensive Data Transformations
~/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.