Remix 3 Drops React: The New Full-Stack Framework Built From Scratch

Hello HaWkers, a piece of news that shook the web development community: Remix 3 has been completely rewritten from scratch and no longer uses React as its foundation. Ryan Florence and Michael Jackson, the framework's creators, decided to rethink full-stack development from the ground up.

This decision was not made on a whim — it reflects a fundamental shift in how we think about web frameworks in 2026.

What Changed in Remix 3

Goodbye React, Hello New Architecture

Remix was always known for embracing web fundamentals — HTML forms, progressive enhancement, and web standards. But with version 3, the creators went further:

Key changes:

No longer depends on React as the UI library
Own reactivity system based on signals
Server-side rendering as the primary default
Native edge computing integrations
AI as part of the framework design process

🔥 Context: When Remix was acquired by Shopify and then merged with React Router, many thought it would be absorbed by the React ecosystem. Remix 3 shows the opposite.

Why Drop React

Ryan Florence explained the decision in a series of posts that generated intense discussion:

1. Native Performance

Without React's abstraction layer, Remix 3 achieves:

Performance gains:

Initial bundle size up to 60% smaller
Faster hydration (no Virtual DOM)
More efficient server-side rendering
Less JavaScript sent to the client

2. Signals Instead of Virtual DOM

Remix 3 adopts signals as its reactivity model, following a trend that Angular, Vue, Svelte, and Solid have already embraced:

// Reactivity in Remix 3 with signals
import { signal, computed, effect } from 'remix';

// Basic signal - reactive state
const counter = signal(0);
const double = computed(() => counter.value * 2);

// Effect reacts to changes
effect(() => {
  console.log(`Counter: ${counter.value}, Double: ${double.value}`);
});

// Update state
counter.value++; // Log: Counter: 1, Double: 2

The advantage of signals over Virtual DOM is granularity: only affected elements are updated, without full tree reconciliation.

3. AI in Framework Design

Florence and Jackson were explicit about AI's role in developing Remix 3:

How AI was used:

AI agents helped test API patterns
Automatic documentation generation
API ergonomics testing with usage simulations
AI-assisted performance optimization

💡 Insight: Remix 3 was designed to be "AI-friendly" — its API is predictable and well-documented, making it easier for AI tools to use.

What Developing with Remix 3 Looks Like

Routes and Data Loading

Remix 3's routing model kept the web standards philosophy but with improvements:

// routes/blog/$slug.tsx - Route with data loading
export async function loader({ params }) {
  const post = await db.posts.findOne({
    where: { slug: params.slug }
  });

  if (!post) throw new Response('Not Found', { status: 404 });

  return { post };
}

export default function BlogPost({ data }) {
  return (
    <article>
      <h1>{data.post.title}</h1>
      <div>{data.post.content}</div>
    </article>
  );
}

// Actions for mutations (forms)
export async function action({ request }) {
  const formData = await request.formData();
  const comment = formData.get('comment');

  await db.comments.create({
    data: { text: comment, postId: formData.get('postId') }
  });

  return { success: true };
}

Native Progressive Enhancement

One of Remix's trademarks is that forms work without JavaScript:

<!-- Works even without client-side JS -->
<form method="post" action="/api/newsletter">
  <input type="email" name="email" required />
  <button type="submit">Subscribe</button>
</form>

With JavaScript enabled, Remix intercepts and sends via fetch, adding loading states and optimistic UI automatically.

The Framework Landscape in 2026

Remix 3's launch happens at a moment of convergence in the framework ecosystem:

Patterns Everyone Is Adopting

Pattern	Next.js	Nuxt 3	Remix 3	SvelteKit	Solid Start
Server Components	Yes	Yes	Yes	Partial	Yes
Signals	Partial	Yes (Vue)	Yes	Yes	Yes
Edge-first	Yes	Yes	Yes	Yes	Yes
Streaming SSR	Yes	Yes	Yes	Yes	Yes
File-based routing	Yes	Yes	Yes	Yes	Yes

The End of Framework Wars?

In 2026, the "which framework to choose" discussion is becoming less relevant because:

Pattern convergence:

All adopt server-side rendering as default
Signals are becoming the universal reactivity model
File-based routing is consensus
Edge computing is a priority for all
TypeScript is required in all

Real differentiation:

Ecosystem and community
Developer experience (DX)
AI tool integration
Performance in specific scenarios
Design philosophy

What This Means for Developers

If You Use React/Next.js

No need to panic. React remains the most used framework and Next.js continues evolving. But it is worth noting:

The signals trend may reach React (React Signals is being discussed)
React Server Components already follow the same direction
Understanding signals now prepares you for the future

If You Use Vue/Nuxt

Vue already uses proxy-based reactivity (similar to signals). You are well positioned:

Nuxt 3 already implements many patterns Remix 3 adopts
The web standards philosophy is shared
Vue 3 Vapor Mode goes in the same direction

If You Use Svelte

Svelte pioneered many of these ideas. Remix 3 validates the approach:

Build-time compilation
Fine-grained reactivity without Virtual DOM
Focus on performance and bundle size

If You Want to Try Remix 3

When to consider Remix 3:

New projects that prioritize performance
Applications that need to work without JavaScript
Edge-first projects
Teams that value web standards

Conclusion

Remix 3 dropping React is not an attack on React — it is a sign that the web ecosystem is maturing. Patterns are converging, good ideas are being shared across frameworks, and developers are the biggest beneficiaries.

What matters most is not which framework you use, but understanding the underlying patterns: signals, server rendering, progressive enhancement, edge computing. These concepts transcend any individual framework.

If you are interested in the evolution of JavaScript frameworks, I recommend checking out another article: Signals: The New Reactivity Pattern Uniting JavaScript Frameworks where you will discover how this trend is transforming web development.

Let's go! 🦅

💻 Master JavaScript for Real

The knowledge you gained in this article is just the beginning. There are techniques, patterns, and practices that transform beginner developers into sought-after professionals.

Invest in Your Future

I have prepared complete material for you to master JavaScript:

Payment options:

1x of $4.90 no interest
or $4.90 at sight

📖 View Complete Content