Implications of the Realtime Web
summary
Claims that Rails 4.0 realtime default makes reactive live apps easier, and demonstrates a chat built with Rails 4.2 plus the action_cable gem that uses Redis pub/sub and websockets. The demo wires two browser sessions, broadcasts messages via a broadcaster, and shows updates arriving in both windows; a background job writes to ActiveRecord after publishing. Meteor and Volt are named as alternative stacks. The demo succeeds at real‑time message sync.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:47Browser Ecosystem
- 5:37Apps of Today
- 10:58Reactive Offline State
- 13:13Why Realtime?
- 14:53Progress Retention
- 17:04Getting Started
