> Dr. Greg Neyman, a resident a year ahead of me in residency, had done a study on the use of ventilators in a mass casualty situation. What he came up with was that if you have two people who are roughly the same size and tidal volume, you can just double the tidal volume and stick them on Y tubing on one ventilator.
This technique was later applied during the COVID-19 pandemic, when ventilators were in high demand and short supply.
> This case involves the NYPD's practice of stopping and searching subway goers without just cause. On July 21, 2005, the NYPD announced that it would begin a new program of searching the belongings of those seeking to enter the subway system. Since the program was implemented, the NYPD has searched tens of thousands of people without any suspicion of wrongdoing. On Aug. 4, 2005, the NYCLU filed a complaint in the District Court on behalf of five individuals. The complaint alleges that the NYPD program violates the Fourth and Fourteenth Amendments...
> On Dec. 7, 2005, the District Court ruled in favor of the defendants and refused the plaintiffs’ request for a permanent injunction. The decision stated that the random subway search program was not “impermissibly intrusive” and was constitutional. The NYCLU appealed to the United States Court of Appeals, Second Circuit. On Aug. 11, 2006, the Second Circuit upheld the District Court decision, stating that the program constitutes the “special need” exception to the Fourth Amendment.
> Researchers in South Korea have found that children between the ages of 10 and 19 can transmit Covid-19 within a household just as much as adults, according to new research published in the US Centers for Disease Control and Prevention journal Emerging Infectious Diseases
>> call a shelter or the related police station and ask how many assaults they have had reported in the past year.
• If assaults happened in shelters, why would the shelters ever tell you?
• Why would anyone ever tell the police? I can't imagine the homeless victims would want the police MORE involved in their lives.
• Even if someone told the police about an assault at a shelter, would they bother to investigate, or keep records? Police have incentives to reduce crime stats, which isn't the same as reducing crime.
Good question. No, the data is downloaded only once.
The server tells the client what requests it's making on the client's behalf.
If the client's JS tries to make a request for a URL that's already in-progress, the client's React-Server code will skip the request and return a promise of the server's streamed response instead.
If the client's JS tries to make a request for something, and the server IS NOT already handling it, then the client will send out an HTTP request, and React-Server will step out of the way.
Hey, I'm a dev at Redfin, and I've done something like this (with Gigabo's help). It's possible, but it's not well-supported yet.
My team owns one special-snowflake API in React-Server. We want the API to be reachable from the client via HTTP, but also want to execute the code directly during server-side rendering, with no HTTP call. It's your exact use-case.
In order to do that, we
1. Detect if the API is invoked server-side.
2. Tell Superagent* to tell the client "hey, if you want data for $API_URL, don't make an HTTP request; the response will come inline in the page's HTML response.
3. Invoke the API code directly.
4. When the API response is ready, serialize it, and tell Superagent to pass it to the client.
We don't do this kind of thing frequently, so we haven't built any graceful tooling for it.
* I _think_ this is Superagent: https://visionmedia.github.io/superagent/https://visionmedia.... Somehow, we use it in a way that notifies the client of what HTTP requests the server is performing on its behalf; not sure if that's stock Superagent or if we added some magic to it.
Each page is split into sections.
Each section may wait for async data and API responses.
When all the data arrives, the section is rendered as an HTML string.
The server streams each section's static HTML to the client as soon as it's ready, and after all prior sections are streamed.
The server also streams the async data to the browser. This avoids the latency of the client downloading some HTML, then downloading some JS, then making the requisite API calls for the page's data. (Think of it as a hacky version of HTTP Server Push.)
On the client-side, React and your JS are downloaded, React will recycle as much of the static DOM as possible (writing isomorphic JS isn't always easy), then take over and do its thing.
"We’ve been using it here at Redfin in production for over a year and it serves the three highest traffic pages on the site. We’re serving 1 billion requests a month from our React Server instance; hundreds of requests per second during peak hours."