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

Michael Jackson Remix has always been the hardest thing to google

Remix 5, we are starting with Firefox fork!

They should rename the entire framework to Premix instead.

Remix 10. We are going to fix the hardware problem the web has.

Preact fans feeling justified in 2025.There are dozens of us, dozens!

My thoughts: - if it’s so different from Remix v2 that there’s literally no upgrade path, they should just call it something else - regardless of the above, I’m very excited to see a framework that uses Preact as its base instead of React and I’m interested to see where this goes and will be watching it closely, but I’m still wondering… - what is going to happen with React Router v7 now, with the team’s attention divided between RR7 and R3. Because of the uncertainty I chose Vite+Wouter instead of RR7 for a client-side todo list (with a fun twist) project that I’m moving off of NextJS for performance reasons. (EDIT: this one was sort of answered by RR7’s move to an OGM) - and also since many libraries for React (notably ShadCN, Tanstack Query and others) do not have compatibility with Preact, what is going to happen in this area? Will this inspire Preact compatibility with more libraries and dependencies?

The web front-end UI is such a perpetual dumpster fire - am loving the renaissance in terminal UI, though

I've been using Remix now for 3 good years (Now React Router V7!) What I've loved about it is how unobtrusive it's been. It's a thin layer that connects the frontend and backend. I've also designed it in such a way (through context injection and CQRS) that I can strip it out of my stack with little to no refactoring effort!

17:56 fun fact, Preact was started before React got published... so...

The excitement is real. Cannot wait to see Remix v3.