The Remix Philosophy is not Just for Remix
summary
Argues Remix’s philosophy generalizes beyond the framework and demonstrates it by building a shopping-list app that uses routes, loader/action functions, server-side Json responses, and in-memory data to add delete and toggle cart state successfully; forms submit as real HTTP mutations and the client bundle hydrates for navigation. Highlights runtime adapters (Cloudflare Deno Bun), ~116 community stacks, roadmap items like Vite integration and loader/action middleware, and that the app runs without JS using forms-as-mutations. GitHub demo exists.
AI-written summary · about
chapters (31)
- 0:00intro
- 0:22preamble
- 0:48about ken
- 1:27why should you care?
- 2:02let's create a real remix app
- 13:18try it on github
- 14:20more complex forms
- 16:29philosophy: embrace server/client model
- 17:21bundles
- 18:13single page app
- 18:39remix app
- 20:10server & runtime adapters
- 20:41official list
- 21:23work with web foundations
- 21:43standards
- 23:09request, response
- 23:48fetch loves requests & response
- 24:26headers
- 25:28url search params
- 26:13traditional react components
- 27:11more traditional react page
- 27:46or just use remix
- 28:07work without js
- 30:11demo without js
- 31:15roadmap and future flags
- 31:43roadmap highlights
- 32:47future flags
- 34:08applying the philosophy outside remix
- 35:11we chose a new mindset
- 36:14hello shoreline
- 36:26thank you
related talks
41mRemix, the hottest JavaScript framework as of today
45mRemix: the Truly Full-Stack Framework
45mWhy I want to do only projects with Remix
20mRemixing How We Give
28mFire-side chat on Remix
54mExploring the World of Remix: A Guide to Building Resilient and Performant Web Apps
48mReact Remixed
26mThe Ultimate Full Stack Framework for 2024: Remix