AI summary by TwinMind

Rails Deserves Better.

Theo - t3․gg

32m 33s

Hey Calendar Performance Issues Demonstration

  • Demo shows slow popup interactions in Hey calendar app (built by Rails creators)
  • Testing with gigabit internet connection in San Francisco - still experiencing jank
  • Drag and drop operations have noticeable lag even with optimal connection
  • Content shift/flicker issues when opening calendar sections
  • Plus button creates empty modal that expands to correct size with delay

DHH Response Prediction and Bingo Board

  • Creator made bingo board predicting DHH's overreaction patterns
  • Expected responses: calling content disingenuous ✓, bringing up no build ✓, mentioning cars ✓, referencing wealth blog post ✓
  • Notes DHH's dated takes and preaching about development approaches
  • Contrasts with more reasonable approaches from HTMX community

Network Latency vs Bandwidth Explanation

  • Distinguishes between two internet speed components:
    • Latency: how fast data moves (time from A to B)
    • Bandwidth: pipe width (how much data can fit)
  • Browser throttling tools only simulate bandwidth constraints, not latency
  • Used VPN to Australia/France to simulate real latency conditions
  • Gigabit connection still experiences delays due to round-trip time

Hey Calendar Under Latency Stress Testing

  • Australia VPN connection: 1.5 second delay for drag/drop operations
  • Multiple rapid interactions cause confused state
  • Plus button takes several seconds to respond
  • Typing before UI fully loads triggers hotkeys incorrectly
  • Enter key submissions have no visual feedback, leading to duplicate events
  • Sends requests on every keystroke
  • 651KB JavaScript loaded initially, more loaded for interactions

Google Calendar Comparison

  • Same Australia VPN latency conditions
  • Create button opens immediately
  • Event creation takes ~200ms vs several seconds
  • Drag/drop works smoothly after first operation
  • Overall "comically better experience"
  • No requests sent on every keystroke

DHH's Dismissive Response Analysis

  • Claims people without modern internet shouldn't use web for calendar/email
  • Mentions Hey doesn't have customers in "Amazonian jungle or Arctic"
  • Announces Amsterdam data center for European customers
  • Dismisses JSON vs HTML performance differences

Technology Spectrum Framework

  • Server-driven vs Local-first spectrum analysis
  • Most applications need hybrid approach between extremes
  • Pure server-driven: blogs, bank websites, video sites
  • Pure local-first: Notion, VS Code, Figma
  • Most apps (including email/calendar) benefit from mixed approach

Framework Positioning on Spectrum

  • Angular: heavily local-first, struggles with server-driven features
  • Rails + Hotwire: server-driven, limited client interactivity
  • Laravel + Inertia: bridge solution combining server backend with React/Vue frontend
  • React + RSC: stretching into server-driven territory
  • HTMX: enables server backends to be more interactive

Community Response Analysis

  • Laravel community embraces client-side solutions (Inertia.js with React/Vue)
  • Taylor Otwell quote: "sizable percentage of new Laravel apps paired with React or Vue"
  • Elixir community adopted similar hybrid approaches
  • Rails community (specifically DHH) refuses to acknowledge limitations

Superhuman Email Comparison

  • Requires Chrome extension for optimal browser experience
  • Works fully offline - can read, navigate, archive emails
  • Syncs changes when connection restored
  • Premium pricing justified by premium experience
  • Demonstrates email apps benefit significantly from local-first features

Performance Metrics and Technical Issues

  • Hey loads 651KB JavaScript initially
  • Additional JavaScript loaded for each interaction
  • 2000 lines of HTML fetched per calendar day click
  • 2 seconds spent in DOM cloneNode operations
  • More JavaScript execution than typical SPAs despite anti-JS stance

Industry Expert Opinions

  • Chris Coyier: most apps need hybrid approach, not full client-side solutions
  • Taylor Otwell: DHH's approach holding Rails back, would delete Hotwire for Inertia
  • Dax: "hate JS but write tons because it delivers high quality apps"
  • Egoist: Hey uses more JavaScript than most applications while claiming to avoid it

Future Technology Direction

  • Bridge technologies are winners: Inertia, Server Components, HTMX
  • Technologies that embrace both sides will succeed
  • Apple copied React components for SwiftUI
  • Laravel copied LiveView for LiveWire
  • Ecosystem improves when ideas cross-pollinate
  • Bar for web experience quality continues rising

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome