473: Mental models for browsers

What It Covers

Joelle Kenville announces her upcoming Pragmatic Press book on web fundamentals and explores mental models for understanding browsers, from HTTP request engines to UI runtimes, examining how front-end versus back-end developers conceptualize browser functionality differently.

Key Questions Answered

• •Browser Core Function: Browsers fundamentally issue HTTP requests graphically through three mechanisms: arbitrary GET requests via URL bar, predefined GET requests through links, and customizable GET/POST requests through forms—understanding this enables reasoning about all web interactions.
• •Platform-Specific Constraints: Each browser operates as a distinct sub-platform with varying capabilities across Chrome, Safari, Firefox, and different operating systems. Testing with tools like Can I Use and the text-based Lynx browser reveals accessibility issues and platform limitations developers must address.
• •Hotwire vs React Decision: Choose Hotwire when state management dominates your problem and visual interactivity is minimal, keeping source of truth server-side. Select React when complex visual interactivity requires local state management, accepting larger initial downloads for subsequent performance gains.
• •Browser as Runtime: Browsers function as complete UI runtimes capable of executing applications offline without HTTP requests. This enables Progressive Web Apps and eliminates learning native frameworks like SwiftUI or GTK, making visual programming accessible to web developers immediately.