Hacker News new | comments | show | ask | jobs | submit login

Where exactly does the React team do that? That's the whole issue: the information is scattered and unless you are plugged into the community, you can't tell truth from opinion from best practice from someone's habit.

The official React tutorial is really basic and provides none of this guidance. The rest of the knowledge is scattered. You can discerne it eventually, but it takes lots of time, and often best practices change.






Are you basically concerned that the React docs don't teach a specific way to build a "complete, production-ready" application, with routing and all the bells and whistles?

Basically. As a newcomer to the platform, I was looking for at least one authoritative way to do things. There can certainly be more, but the fact that I have to seek out not "how to lay out a React app" but "who are the big names in the React community" makes for an unnecessary hurdle.

I am all for diversity of approaches, but there is no good starting point. So I spent days searching, comparing, etc.

Your list is great. It is not the only one. How do I know that yours is "correct"? The only answer is comparing which links show up frequently on various lists. That is so much more time consuming that having an official list or tutorial.


Yeah, there really is _no_ absolute "authoritative" way to do things in the React world. People use React to write complete SPAs with server rendering and client-side routing, and the latest build tools. People also use React to add a few widgets to existing static HTML, or with no build tools at all. They use it for developing web applications, native applications, and for really crazy stuff like creating sample-driven music, presentations, and driving hardware.

So, what would "authoritative" docs look like, given those wide varieties of use cases? The closest thing there is at the moment is the Create-React-App tool, which is deliberately opinionated about setting up a build tool system with certain behaviors, but is otherwise unopinionated about all other libraries and file structures you might choose to pull in.

The core React team is pretty small - currently like 7 people. They have to split their time between actually working on the library, and dealing with Facebook's internal needs. On top of that, the way Facebook uses React is going to be different than the way much of the community uses React, due to Facebook's unique and specific infrastructure.

For lists: yeah, there's some other useful lists out there. I actually point to them in the "Community Resources" category of my list. There was an issue discussing a possible new "Learning Resources" section for the React docs as part of the docs revamp ( https://github.com/facebook/react/pull/7117 ), which bogged down a bit due to concerns about endorsing specific libraries. There's currently an open issue regarding further additions to the docs that looks like a request for the community to contribute sections on specific topics ( https://github.com/facebook/react/issues/8060 ).

As for my own list: I put multiple hours into updating it every week, between reading articles, evaluating them, and categorizing them. I won't say I've read every word of every article, but I've definitely looked at each and every article in the list and determined that it's relevant and of good quality. Beyond that, I'd say that the nearly 6000 stars are a reasonable indicator that a lot of people are finding my list useful.


To be fair, Vue and Angular 1 and 2 all have pretty comprehensive getting started tutorials that don't teach you just a small part of the platform, but all of it. Sure, you can use Vue to just make a funny web component that's a part of a normal app, but that's not the main focus.

With the React ecosystem, it's basically equivalent to the Django template system having documentation, but the rest of the info being scattered across dozens of personal blogs.

The React team, being the face of the ecosystem, would do well to point newcomers to a list such as yours.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: