AI summary by TwinMind

Remix is ditching React (and I think that's a good thing)

Theo - t3․gg

27m 39s

Remix History and Evolution

  • Started as paid template alternative to create-react-app by Michael Jackson and Ryan Florence (React Router creators)
  • Originally wrapper for React Router meant to be paid template
  • Built on ESBuild (super new at time), heavy server-side loader patterns
  • Expanded team, brought Kent Dods for education/DX
  • Took investment from OSS fund, then open sourced
  • React Router stagnated during Remix development period
  • React Router V7 became phenomenal release after renewed focus

Shopify Acquisition and Market Context

  • Next.js exploded while Remix was being built (barely used when Remix started, massive when acquired)
  • Shopify built Hydrogen meta framework in parallel
    • First to bet heavily on React server components
    • Used very early version, got burnt badly
    • Backed away from React standards entirely
  • Shopify acquired Remix team instead of continuing Hydrogen
  • Three framework approaches at time: building along React (Hydrogen), alongside React (Next.js), opposite direction (Remix)

React Router V7 Success and Remix Merger

  • Post-acquisition focus shifted back to React Router development
  • Moved from ESBuild plugin hell to Vite-based approach
  • Remix V2 became thin wrapper around React Router
  • Merged Remix features into React Router V7 framework mode
  • Added server component support to React Router
  • Happy migration path from Remix V2 to React Router V7
  • OpenAI codebase currently structured this way
  • Effectively killed original Remix to give room for rethinking

Remix V3 New Direction - Abandoning React

  • No longer tied to specific paradigm (React)
  • Reimagining of web framework from first principles
  • Focus on simplicity, clarity, performance without losing developer power
  • Modular toolkit approach
  • Full stack ownership without external abstraction layers
  • No critical dependencies, not even React
  • Starting with fork of Preact (mature virtual DOM library)
    • Used heavily at Shopify, Google
    • Built as minimal React alternative
    • Strict 3KB threshold rules
    • Originally created by former Meta employee

React Router V7 Transition to Open Governance

  • React Router powers: Shopify, X.com, GitHub, ChatGPT, Linear, T3 Chat
  • Moving to open governance model (not fully owned by Ryan/Michael)
  • Dedicated team, long-term backing
  • One minor release away from full React architecture support
  • Community-run to prevent single ownership issues

Remix V3 Core Principles

Model First Development

  • AI fundamentally shifts human-computer interaction
  • Optimize source code, documentation, tooling for LLMs not just humans
  • Develop abstractions for applications to use models in products
  • Current frameworks poor at streaming AI responses, UI updates per token
  • Framework built for simple, concise solutions LLMs can understand

Building on Web APIs

  • Use web standards extensively
  • Same patterns server vs client side
  • Avoid different versions for node vs client files

Religiously Runtime

  • Avoid compiler tricks for functionality
  • Code written should be very close to code run
  • Only differences: remove type definitions, turn JSX into functions
  • No complex bundler interventions like server components require

Zero Dependencies Goal

  • Tired of dealing with other people's roadmaps
  • Choose dependencies wisely, wrap completely
  • Expect to replace most with own packages eventually
  • Goal is zero dependencies

Demand Composition

  • Abstraction should be single purpose, replaceable
  • Every package useful/documented independently
  • New features attempted as new packages first
  • Tightly coupled modules that change together should be same package

Distribute Cohesively

  • Extremely composable ecosystems difficult to learn/use
  • Packages wrapped in single package as dependencies
  • Reexported as single toolbox (Remix)

Market Context and Comparisons

  • Nobody rethought Express since React/TypeScript emerged
  • Existing solutions (Fastify) just faster Express, not rethinking
  • No application-first Express with modern needs
  • Current tools focus on JSON/HTML responses, not unique context per application need
  • Opportunity to rethink URL-to-experience pipeline from first principles
  • Comparison to Rails but using web standards instead of English-like syntax
  • Building using browser standards as shared language between server/client

Technical Implementation Details

  • Starting from server request handling to browser rendering
  • Rethinking multiple layers in pipeline
  • Focus on making building good applications easier for humans AND LLMs
  • Timing critical - one of last moments this type of fundamental rethinking possible
  • Bringing back Reach UI as built-in component library
  • First-class database drivers included

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