It's not what I expected, but maybe what we need

The video introduces Remix v3 as a new full-stack JavaScript framework created by Ryan Florence and Michael Jackson, the original authors of React Router and Remix JS. The speaker acknowledges viewer skepticism about yet another JavaScript framework but emphasizes this one is particularly interesting given its creators' credentials. The framework represents a complete reimagining rather than an iteration, as Remix v2 was merged with React Router in 2024. This sets the stage for understanding why the Remix brand is being repurposed for an entirely new framework built from scratch, independent of React.

This section explains Remix's history and evolution to provide context for the new framework. Remix was originally released as a React meta-framework around 2022, serving as an alternative to Next.js. In 2024, Remix v2 was merged with React Router, allowing React Router to function both as a traditional routing library and in 'framework mode' for full-stack React applications. This merger raised questions about the future of the Remix brand, which is now being answered with v3 as a completely new framework. The speaker emphasizes that unlike its predecessor, Remix v3 is not a React meta-framework but rather an independent full-stack JavaScript framework written from scratch, incorporating all the features and APIs the creators wanted to implement based on their extensive experience.

The video dives into one of Remix v3's most controversial features: the 'this.update()' method that requires developers to explicitly trigger UI updates. Unlike React, Vue, or Angular where frameworks automatically determine when to re-render, Remix requires manual calls to 'this.update()' after changing state variables. The speaker explains that developers manage state in standard variables without hooks like useState, and they have complete control over when the UI updates - you can change multiple variables without updates, or trigger an update when ready. While acknowledging that this approach differs from established patterns and has drawn criticism online, the speaker suggests it could solve problems with the automatic approach, particularly in complex apps where it's unclear why something updates or doesn't. The manual control aims to provide a simpler, more predictable API where developers have full transparency.

This section explores Remix v3's core design principles, particularly its focus on web primitives and large language model compatibility. The framework heavily relies on native browser capabilities like built-in event systems, custom event dispatching, and abort signals for handling component unmounting, rather than creating custom abstractions. The creators stated in a blog post that a clear goal is making the framework easy for LLMs to use, as none of the existing models were trained on this new codebase and 80% of frontend examples are React-based. The simple, expressive API is designed so developers can feed documentation into chat contexts and have AI assistants generate code effectively. The speaker notes that web developers haven't kept up with modern browser capabilities that have existed for years, and Remix aims to leverage these built-in features to keep the framework lean and avoid unnecessary third-party libraries.

The framework's component system is explained, showing how it uses JSX and functions rather than DOM manipulation APIs, but with a crucial distinction from React. Remix v3 introduces two types of component functions reminiscent of pre-hooks React: stateless components that simply return JSX, and stateful components that return a function which then returns JSX. The outer function is called once, while the inner function can be re-executed when 'this.update()' is called. Stateless components can accept props and re-render when parents update, but cannot manage their own state. This creates a clear, simple distinction between component types without requiring classes or hooks. The speaker emphasizes that component functions won't be called repeatedly like in React; instead, only the returned function in stateful components gets re-executed, providing a more controlled and predictable rendering model.

Remix v3 is positioned as a full-stack framework with comprehensive backend capabilities, not just a frontend solution. Building on the team's decade of router development experience, it includes a powerful router for the backend with support for returning JSX and hydrating Remix components on the server. The framework introduces its own alternative to React Server Components that allows simpler server-side rendering patterns. When clients send requests (like deleting an item), the server can return HTML that gets hydrated to update parts of the DOM, enabling snappy, modern single-page-application-like experiences. Additionally, they're shipping a component library to simplify building complex forms. The goal is to provide all the features available in frameworks like Next.js, React Router framework mode, or TanStack Start, but with a dramatically simpler API and development experience, maintaining consistency with the framework's overall philosophy of simplicity.

The speaker addresses the critical question of whether the JavaScript ecosystem needs another framework, acknowledging the crowded market and common sentiment of 'too many frameworks.' However, he argues that innovation and trying new ideas is valuable, distinguishing Remix v3 from frameworks that merely copy React with minor differences. The manual update approach and other novel features represent genuinely new ideas worth exploring. The speaker believes it could provide a simpler alternative to React, which has grown increasingly complex over the years. Regarding AI concerns, he notes that while LLMs typically recommend React, experienced developers remain the primary audience. These developers can steer LLMs to generate Remix code using official examples, as they still touch, tweak, and write code themselves despite AI assistance. The speaker emphasizes that developers still care about their tech stack and having a simple, AI-friendly framework could be compelling.

The final section analyzes Remix v3's chances of success, with particular emphasis on Shopify's ownership as a crucial advantage. Shopify acquired Remix in 2022, and the speaker speculates that the framework could become an option for Shopify vendors building custom shop fronts and pages. Having an easy-to-use framework that works well with LLMs could be transformative for the Shopify ecosystem, though success isn't guaranteed. Beyond corporate backing, Remix has a small but enthusiastic community and the creators have an excellent track record from developing React Router. The speaker expresses excitement about eventually using the framework himself, noting it's not currently available for public use. He concludes optimistically about Remix's potential while acknowledging the challenges of entering a crowded market, encouraging viewers to share their thoughts on whether the framework is needed and whether it will succeed, and pointing them to the full four-hour conference presentation for more details.