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

React Server

react-server.io

Post reply on HN
Print view View original

61–70 of 143 posts

Re: React Server

#61

Post by davidalber »

hyperpape wrote: post #55
davidalber wrote: post #51

Earlier quoted context omitted.

gigabo's account has been rate limited, but he wants to say: "Well... we made it through the first hour or so of HN traffic on a single t2.medium instance in ec2 before we started seeing errors. We're now on three m4.larges with good head room. Not too bad, I think? We meant to get cloud front set up before we got this sort of traffic, but glad to be surprised with an early bump. :)" This is me saying this: I think w…

I honestly don't know, what's the actual requests/second for that? I don't have a good feel for what HN traffic is like. From one post ( https://news.ycombinator.com/item?id=8107658 ), it seems like a few thousand hits/hour over a fraction of a day, but (1) there's a lot of variation, (2) it doesn't tell you the peak rate

We were seeing around 450 active users on the site at the peak. We currently have around 220 active users that are generating about two page views per second, peaking to six page views per second. That's about where we were when we scaled up from a single t2.medium instance.

Re: React Server

#62

Post by davidalber »

kough wrote: post #49
gigabo wrote: post #9

Earlier quoted context omitted.

Yes, definitely agree! We need better tutorials! We need better docs in general. Contributions welcome! :D

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

gigabo's account has been rate limited, but he wants to say:

Oh, hey didn't mean to sound flippant there! We're definitely planning to make tutorials, and we're constantly trying to improve our docs. I guess my point is we want this to happen faster, but we're still a pretty small project with a small team of core contributors. So we're thrilled when we're able to bring in new contributors to help out!

Re: React Server

#63

Post by idbehold »

wwalser wrote: post #48
idbehold wrote: post #42

How does it handle fetching data from a path on the same origin? For instance, I only need to fetch('/api/users.json') on a certain page (/users). This means that it can either be hydrated in the initial state when performing a full page load of /users or needs to be fetched (using xhr/fetch) when navigating to that page from another page on the site (which shouldn't require a full page load). So how exactly does the…

The other responses seem to be answering how this would work once the hydration is occurring on the client side. I understood the question to be `Does the http request layer support doing API requests to routes which are on the same webserver as react-server`. There doesn't appear to be special handling for this use case. However, they use SuperAgent ( https://github.com/visionmedia/superagent ) for http requests and…

What I'd like to be able to do is not incur an additional HTTP request against my own server. Does SuperAgent have a way to avoid opening a new socket when making a request against yourself?

Re: React Server

#64

Post by AShedOfTools »

kough wrote: post #49
gigabo wrote: post #9

Earlier quoted context omitted.

Yes, definitely agree! We need better tutorials! We need better docs in general. Contributions welcome! :D

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

I completely agree. If you take a look at the closed prs with the label documentation (https://github.com/redfin/react-server/pulls?utf8=%E2%9C%93&...) I hope you get the sense that this is something that I'm thinking about a lot, and that if you look at the issues open with the same label (https://github.com/redfin/react-server/issues?q=is%3Aissue+i...), that it's something I'm working on actively. There are lots of ways to document a healthy project, from tests to tutorials to docs sites to good examples, and we've been working hard on markdown docs, tests and examples because they allow us to scale to having more contributors faster. Striking a balance between kinds of documentation is hard, and its even harder to strike a balance between the rest of the project's needs and documentation. This is a technology that we run in production, and so we have to make sure that it is fast and stable and reliable, and sometimes that means giving short-shrift to other priorities. I'm not trying to absolve us of any short-comings in our documentation -- we have a lot to do in the coming years to improve this project, and we need to spend time writing tutorials and user testing the on-boarding experience for new devs that want to start up their first React Server project -- but I do want you to understand where we're coming from when we say "contributions welcome." Its just pragmatic; we're working on it as hard and as fast as we can, its a priority I continue to focus on, and if you want it faster, the best way is to chip in.

Re: React Server

#65

Post by AShedOfTools »

bphogan wrote: post #54
kough wrote: post #49

Earlier quoted context omitted.

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

I have to agree here. There's nobody better to explain how something really works than the person who wrote it. The rest of us are just fumbling around guessing. As a dev and a creative person, I understand the desire to get something out there. But documentation and tutorials aren't just something that's nice to have. They are your marketing tool, your adoption driver, and the way to create educated advocates for yo…

That process of you fumbling around and guessing is actually really extraordinarily helpful. The things a contributor might think to do or to try, and the things that a newcomer might think to do or to try, are completely different. No documentation survives its first encounter with a real newcomer. We can, and will, continue working on the onboarding experience, but we'll need real users to roll up their sleeves and wade into it, and the first few of them will have questions we didn't anticipate, and make assumptions we've never considered, and try use cases we've never thought of. Creating good documentation is something that newcomers and contributors need to collaborate on.

Re: React Server

#66

Post by kough »

AShedOfTools wrote: post #64
kough wrote: post #49

Earlier quoted context omitted.

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

I completely agree. If you take a look at the closed prs with the label documentation ( https://github.com/redfin/react-server/pulls?utf8=%E2%9C%93&... ) I hope you get the sense that this is something that I'm thinking about a lot, and that if you look at the issues open with the same label ( https://github.com/redfin/react-server/issues?q=is%3Aissue+i... ), that it's something I'm working on actively. There are lot…

OK, you definitely get it :) Love what you wrote below:

"No documentation survives its first encounter with a real newcomer."

I hope it didn't seem like I was accusing you of negligence – the docs you have are an awesome start, and I fully appreciate the difficulty of the problem. Best of luck with things going forward, looks like a really neat project.

Re: React Server

#67

Post by [deleted] »

kough wrote: post #66
AShedOfTools wrote: post #64

Earlier quoted context omitted.

I completely agree. If you take a look at the closed prs with the label documentation ( https://github.com/redfin/react-server/pulls?utf8=%E2%9C%93&... ) I hope you get the sense that this is something that I'm thinking about a lot, and that if you look at the issues open with the same label ( https://github.com/redfin/react-server/issues?q=is%3Aissue+i... ), that it's something I'm working on actively. There are lot…

OK, you definitely get it :) Love what you wrote below: "No documentation survives its first encounter with a real newcomer." I hope it didn't seem like I was accusing you of negligence – the docs you have are an awesome start, and I fully appreciate the difficulty of the problem. Best of luck with things going forward, looks like a really neat project.

[deleted]

Re: React Server

#68

Post by AShedOfTools »

kough wrote: post #66
AShedOfTools wrote: post #64

Earlier quoted context omitted.

I completely agree. If you take a look at the closed prs with the label documentation ( https://github.com/redfin/react-server/pulls?utf8=%E2%9C%93&... ) I hope you get the sense that this is something that I'm thinking about a lot, and that if you look at the issues open with the same label ( https://github.com/redfin/react-server/issues?q=is%3Aissue+i... ), that it's something I'm working on actively. There are lot…

OK, you definitely get it :) Love what you wrote below: "No documentation survives its first encounter with a real newcomer." I hope it didn't seem like I was accusing you of negligence – the docs you have are an awesome start, and I fully appreciate the difficulty of the problem. Best of luck with things going forward, looks like a really neat project.

Aw shucks :) Thanks!

Re: React Server

#70

Post by jzelinskie »

kough wrote: post #49
gigabo wrote: post #9

Earlier quoted context omitted.

Yes, definitely agree! We need better tutorials! We need better docs in general. Contributions welcome! :D

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

"Contributions welcome" is often echoed, but I like to remind colleagues that it is not the proper mentality to foster a real community. You can't just dump code on GitHub and assume the world is going to start firing off PRs to do your dirty work. You have to assume that no one else cares about your project, but being open to changes in code and leadership will make your project more robust to other use cases.
Post reply on HN