Web-Standards-First Frameworks

Frameworks built on native browser primitives (Fetch API request/response routing, unbundled dependencies, server-driven UI/frames) instead of framework-specific abstractions, betting that web-standards conformance outlasts any one framework's abstraction layer.

Also known as: web standards first, unbundling (framework), Fetch API routing, server-driven frames, framework-specific abstractions (avoiding)

Documents (1)

• Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework Daniel Curtis · 2026-07-28 source ↗ Reader 🖥️
  Remix 3's beta preview is a ground-up architectural break from Remix 2 — dropping the React runtime for a forked, imperative Preact, rebuilding routing on raw Fetch/Response objects, and introducing server-driven 'frames' and a bundler-less 'unbundling' model — a deliberate bet that web-standards conformance beats framework abstraction, one so disruptive that it forces every existing Remix app into a full rewrite and has split developer commentary between praise for its explicit simplicity and skepticism toward a team already known for reinventing itself.

Open gaps (4)

• incompleteThe article never explains what 'unbundling' concretely means for build tooling in practice — how source maps, tree-shaking, code-splitting, or third-party bundler-dependent tooling are handled once 'the runtime rather than a bundler is the source of truth' — so readers cannot assess the real tradeoffs of dropping the bundler model.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: Remix 3's own documentation/source once the beta stabilizes; comparisons with other runtime-first, no-bundler approaches (e.g., Deno's native TypeScript execution, import maps) to see what unbundling typically costs or saves.
• incompleteThe article reports that a forked Preact replaces the React runtime but never quantifies the performance, bundle-size, or ecosystem-compatibility implications (e.g., React DevTools, existing React component libraries) of forking Preact rather than adopting it unmodified or retaining React.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: Benchmarks and compatibility write-ups once Remix 3 ships stable; the fork's own diff/changelog against upstream Preact.
• illogicalThe article asserts Remix 3 is 'the boldest bet yet on web standards over framework abstractions' against Next.js, SolidStart, and SvelteKit, but never tests whether Remix 3's claimed full-stack breadth (auth, uploads, data/database management, theming) is actually delivered with comparable maturity to those competitors — the comparison is asserted, not demonstrated.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: A hands-on feature-parity comparison across Remix 3, SvelteKit, and SolidStart on the specific claimed full-stack capabilities.
• uninformedThe article does not explain why the team chose to keep JSX as authoring syntax while dropping React's virtual-DOM/reconciliation model entirely — a design tension between 'web standards' purism and retaining a React-shaped authoring surface that is never addressed or justified.
  Remix 3 Beta Preview Ditches React for a Web-Standards Full-Stack Framework — read next: The team's own 'Wake Up, Remix' rationale post; any interviews with Michael Jackson explaining the JSX-retention decision.