Viewing profile — ryanflorence

Remix co-author here. We haven't "missed on RSC", they aren't even released! We already have experimental versions of Remix running on React 18 and have experimented with RSC, Susp…

Remix co-author here. Infinite scroll/pagination is a great way to test the limits of a web framework! Remix doesn't ship an infinite scroll/pagination set of components so it's up…

Author here. One more time for those in the back: v0.x > v1 Breaking changes v1 > v2 > v3 a couple obscure breaking changes, but practically none 18 months pass v3 > v4 New, compos…

Jimmy. Jimmy 2020, my man. Did you click the link? Did you notice how every link on the page links to a free video? Did you see the paragraph at the top of the page explaining that…

Sorry about that, meant to say "lectures" not "videos" ... But I mean ... the videos for every pattern is free, so if we're gonna split hairs the title is correct!

Not any time soon, gotta pay the bills somehow! :P

Following stable releases we had one breaking API change in 2 years from 0.13 -> 1.0. 2.0 was fully BC, 3.0 removed 1.0 API 8 months after 2.0 was released. People shouldn't instal…

Also, don't upgrade. v3 is going to maintained with bugfixes and whatever needs to happen to be compatible with new React releases indefinitely.

I'm so confused. There are only two actual releases there: v2.0.0 and then 8 months later v3, where all that happened was v1 API was removed. If you only keep up with the stable re…

also, not every app wants to do it the same way. Now that we're Just Components™ you can handle scrolling however you'd like.

you get location.search, which is just a string. We removed default query handling because it can be composed in with something like `RouteWithQuery` and `LinkWithQuery`. Lots of p…

We had breaking changes from 0.13 -> 1.0. We had no breaking changes from 1.0 -> 2.0. That's 2 years with no breaking changes. Our workshops have $899 early bird tickets. Every sof…

0.13 -> 1.0 was breaking 1.0 -> 2.0 was fully BC That was 2 years with only one breaking change. 2.0 -> 3.0 removed deprecated 1.0 API, fully BC with 2.0 The only churn is for peop…

1) Not sure why navigating is "more complex on native". The platform the code runs on has nothing to do with the way the user interacts with the page. Complex navigation state is r…

> backcompat-breaking changes to React-Router We had breaking changes from 0.13 to 1.0. Then complete BC from 1.0 to 2.0 That's two years, one breaking upgrade. Don't confuse a lib…

Difference is the API. React Router is a 100% declarative components, rather than configs and imperative actions.

only have time for so many things, v1 final release will have a site that works well on mobile too.

browsers are handling that now https://majido.github.io/scroll-restoration-proposal/history...

We're working on an upgrade guide, but in short, it's a completely different library. Major difference is that routes are actual components that are actually rendered, where before…

Neither were we >.< but we were learning React along with everybody else! You'll love this version.