Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React Router: Declarative Routing for React

reacttraining.com

Post reply on HN
Print view View original

61–68 of 68 posts

Re: React Router: Declarative Routing for React

#61

Post by ryanflorence »

ryanflorence wrote: post #14
arrakeen wrote: post #10

i like the power of the new API but i'm not sure i'm entirely sold on the declaration syntax. adjacent tags which specify things that may appear in the same place depending on the route seems a bit strange conceptually to me. i'll have to play around with it on a real-world project to see how it feels in practice. i didn't see it mentioned in the docs, but does the new version fix the awkward handling of scrolling an…

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

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.

Re: React Router: Declarative Routing for React

#62

Post by ryanflorence »

colept wrote: post #46
ryanflorence wrote: post #44

Earlier quoted context omitted.

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 that's their own problem.

v2.0.0 released this on Feb 10, 2016 v3.0.0-alpha.1 released this on May 19, 2016 v3.0.0-alpha.3 released this on Aug 2, 201 v3.0.0-beta.1 released this on Sep 16, 2016 v4.0.0-0 released this on Sep 13, 2016 v3.0.0 released this on Oct 24, 2016 > ... and that's their own problem. Hence deprecation right out the gate. V4 is much better, great work - but blaming users for API churn does not make me confident. Sure user…

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.

Re: React Router: Declarative Routing for React

#63

Post by ryanflorence »

colept wrote: post #46
ryanflorence wrote: post #44

Earlier quoted context omitted.

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 that's their own problem.

v2.0.0 released this on Feb 10, 2016 v3.0.0-alpha.1 released this on May 19, 2016 v3.0.0-alpha.3 released this on Aug 2, 201 v3.0.0-beta.1 released this on Sep 16, 2016 v4.0.0-0 released this on Sep 13, 2016 v3.0.0 released this on Oct 24, 2016 > ... and that's their own problem. Hence deprecation right out the gate. V4 is much better, great work - but blaming users for API churn does not make me confident. Sure user…

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

Re: React Router: Declarative Routing for React

#64

Post by ryanflorence »

tga wrote: post #47

I was going to complain about churn and such, but we've all heard the JavaScript framework fatigue story a thousand times. I'll summarize it to this: don't expect a solid, stable, boring library to come out of someone's hobby project. React itself bloomed under Facebook's stewardship, while all the other libraries in the ecosystem are bouncing all over the place without anything to keep them in place, especially afte…

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 to us about it.

Re: React Router: Declarative Routing for React

#66

Post by tm33 »

vmasto wrote: post #57
triplezero000 wrote: post #55

Earlier quoted context omitted.

False analogy - RR is a de-facto standard in the web development community, hence my comparison to a building code.

No, RR is the de facto standard for the React community. And they're not doing training just on RR. Claiming that because they made the most popular routing library for React it's shady to provide tutoring about it for profit is very much of a stretch in my book. Care to explain where exactly is the conflict of interest? Does that mean it's also shady to work as consultants? Where is the line drawn? Do you really bel…

Ironically we typically spend less than 5% of a workshop talking about the router. So saying that we make breaking changes to sell tickets to our workshops is just naive. I can see how that's a gut reaction though, so no judgement on my end.

Re: React Router: Declarative Routing for React

#67

Post by tm33 »

browniefed wrote: post #58
mxstbr wrote: post #23

Earlier quoted context omitted.

Out of curiosity, why was the decision made to build a completely new router (react-navigation) vs collaborating on better native support to the existing react-router? (which is working towards that anyway)

Difference in opinions about what could be accomplished via react-router vs what native paradigms needed to be crafted.

Do you have a list of these native paradigms anywhere?

Re: React Router: Declarative Routing for React

#68

Post by jashmenn »

chubasco wrote: post #45
jashmenn wrote: post #40

Earlier quoted context omitted.

Yes, we're fixing that as we speak. It will be up to date shortly.

I am considering buying this for an engineer that works for me to get up to speed on React in the very near future. I only want to start him on ES6+ syntax though. How long do you think until it will be up-to-date?

The first chapter has already been updated to use ES6 class syntax, and we explain how it works there. We're converting the rest of the book to use ES6 classes (and removing createClass) over the next week or two.
Post reply on HN