Matt Brophy
@brophdawg11.com
790 followers 210 following 420 posts
Helping folks build better websites Remix/React Router @Shopify 💿 Philadelphia
Posts Media Videos Starter Packs
Reposted by Matt Brophy
I just created the “Remix 3 Resources” repo, collecting useful links related to Remix 3.

It has *super* granular links to the Remix Jam live stream for each API, feature and demo, plus a bunch of demo apps and 3rd party integration examples.

github.com/markdalgleis...
GitHub - markdalgleish/remix3-resources: A collection of useful links relating to Remix 3
A collection of useful links relating to Remix 3. Contribute to markdalgleish/remix3-resources development by creating an account on GitHub.
github.com
This is why we can’t have nice things 😂
Sick enhancement from @rossipedia.com here.

Now I need to hear sick beats from all of you since I'm not musically talented. Added some logic to sync the beat to the URL and deployed to GH pages. Share your beats in the replies!

brophdawg11.github.io/remix-jam-mk...
Once I finish battling github pages we'll be able to actually share these
I like to think we brought the excitement to a much larger community in RR personally. Download counts aren't the best metric, but RR was 20x the size of Remix at the time of v7. We've seen RR nearly double since we released v7 a year ago while it had been mostly stagnant in the year prior.
The upgrade path is Remix v2 -> React Router v7 and is non-breaking- that's a very easy sell.

There's no intended "migration path" from Remix v2/RR v7 to Remix 3, so there's nothing to sell there.

It is very much a new thing, but still trying to solve what Remix set out to solve originally IMO
This is related to another core issue

Migrating from RR to Remix was "easy" - swap a few packages, adopt incrementally, etc.

But sounded scary to bosses - no budget to "migrate to Remix" which hurt adoption

It was never a migration, it was an incremental upgrade - which is formalized with RR v7
Remix v1 proved out a slew of new ideas. It took a lot of work to port those back to React Router, but it made no sense to continue to restrict those features to a new framework (requiring SSR at the time). There were tons of React Router SPAs out there that deserved them.
In some ways, React Router ate Remix

I can't speak for Michael and Ryan, but IMO Remix has always been about embracing the server, the platform, and HTTP

Remix v1 did that on top of React and React Router

Remix 3 takes that further and removes dependencies so it can truly own the full stack
*record scratch* *freeze frame* Yep, that's me (Remix 3). You're probably wondering how I got here.

This is how I like to visualize/explain the evolution of Remix and React Router. I was nerd sniped by a diagram @bradwestfall.bsky.social posted the other day so I finally put pen to paper
No - I think anything trying to be everything is doomed to fail. To much breadth, never enough depth.

The beauty is that the primitives, APIs, inherent simplicity, and lack of magic enables you (the app developer) to do a lot of interesting things with it.
Minus the React integration 😉
yeah the event only scratched the surface of what this will unlock IMO
The Remix 3 server-side router is `fetch` based

which means it also runs in the browser

which means you can build a SPA router on top of it

with fine grained event-driven rendering if that's your jam

(it could also live in a service worker)

stackblitz.com/edit/vitejs-...
Vitejs - Vite (duplicated) - StackBlitz
Next generation frontend tooling. It's fast!
stackblitz.com
please share so I can make sick beats
Early adopter indeed 🙌
I’m reaching the age of “checking my bag is just objectively easier so I don’t have to lug it around the airport and the 10-20 minutes to pick it up at the end don’t actually impact my trip” 👴🏻
Nice talk man! I was able to listen to the livestream on my drive to the airport. I’ll have to go rewatch the video once it posts
This is definitely not the case and is the reason I’m not playing golf with @jim-nielsen.com and @ricky.fm this week
Gotta wonder if the Remix folks intentionally planned Remix Jam the same week as React Conf, just two days day after 😳