~/talk

Re-graphing The Mental Model of The Rails Router

Talkat RailsConf 2018 · 2018-04-17..04-19· [ruby-on-rails, web-platform]

A concrete claim: the Rails router is implemented as a graph engine (Journey) that tokenizes URLs with a scanner, parses them into syntax trees, then composes those trees into a generalized transition graph (a nondeterministic finite automaton) to match routes in sublinear time. The talk runs through the surprisingly large 123 slides of examples, shows the built-in rails.application.routes.router.visualizer, and demonstrates the visualizer working as a practical debugging tool that exposes the NFA and explains no route matches.

AI-written summary · about

  1. 0:00Intro
  2. 5:54Investigating the Router
  3. 12:10Comparing to the Post Office
  4. 14:38Journey in the Router
  5. 20:28How Router Reads
  6. 22:10Tokenization
  7. 24:24Parser
  8. 25:11Syntax Trees
  9. 27:21Journey
  10. 31:15Two Outcomes
  11. 34:33Conclusion
~/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.