ryanflorence

7 ms·

1.
by ryanflorence 5y ago
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, Suspense, and streaming extensively. In thei
2.
by ryanflorence 5y ago
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 to apps to make sure that state is sti
3.
by ryanflorence 7y ago
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, composable design, basically a new project v3 still
4.
Reach Router: Accessible Router for React.js(reach.tech)
8 points by ryanflorence 8y ago|0 comments
5.
Workshop.me, Training on Vue, React, Webpack and More from OSS Maintainers(workshop.me)
12 points by ryanflorence 9y ago|0 comments
6.
by ryanflorence 9y ago
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 these free videos are part of a larger course? No? Huh.
7.
by ryanflorence 9y ago
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!
8.
by ryanflorence 9y ago
Not any time soon, gotta pay the bills somehow! :P
9.
React Training's Advanced React.js Patterns Videos Now Free(reacttraining.com)
120 points by ryanflorence 9y ago|13 comments
10.
Free Updated React (v15.5) Course by the Creators of React Router(reacttraining.com)
35 points by ryanflorence 9y ago|6 comments
11.
by ryanflorence 10y ago
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 install beta/alpha like its stable and then complain
12.
by ryanflorence 10y ago
Also, don't upgrade. v3 is going to maintained with bugfixes and whatever needs to happen to be compatible with new React releases indefinitely.
13.
by ryanflorence 10y ago
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 releases your life has been simple with React Router.
14.
by ryanflorence 10y ago
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.
15.
by ryanflorence 10y ago
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 people didn't want the default serialization anyway. It&
16.
by ryanflorence 10y ago
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 software company I've ever worked for sells tra
17.
by ryanflorence 10y ago
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 people who don't stick to stable releases, and tha
18.
by ryanflorence 10y ago
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 represented as one or many stacks of URIs. 2) In Re
19.
by ryanflorence 10y ago
> 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 libs "changing API" with "people us
20.
by ryanflorence 10y ago
Difference is the API. React Router is a 100% declarative components, rather than configs and imperative actions.
21.
by ryanflorence 10y ago
only have time for so many things, v1 final release will have a site that works well on mobile too.
22.
by ryanflorence 10y ago
browsers are handling that now https://majido.github.io/scroll-restoration-proposal/history...
23.
by ryanflorence 10y ago
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 they just had their props stripped and plugged in
24.
by ryanflorence 10y ago
Neither were we >.< but we were learning React along with everybody else! You'll love this version.
25.
by ryanflorence 11y ago
I went back to component state.
26.
by ryanflorence 12y ago
1. Solve something that hasn't already been solved well 2. Have a ton of examples in the repository 3. Use it in production in your own stuff 4. Keep a solid change log and upgrade guide 5. Ignore the stars, all of this is for your tea
27.
by ryanflorence 12y ago
If you read the overview you may understand our opinion that "application state" is precisely which views to render. https://github.com/rackt/react-router/blob/master/docs/guide... We&#x27
28.
by ryanflorence 12y ago
We've almost tied all the knots we need to meet this requirement of a router. Every application has UI nesting at the core of its state, though.
29.
by ryanflorence 12y ago
Then use them as JavaScript functions, because that's what they are :) The point of JSX is to express attributes and hierarchy, which matches with our route configs perfectly.
30.
by ryanflorence 12y ago
I'm one of the authors of react router. How do you feel about <script/> tags, or <link/> or <meta/> or <base/>?

More ›