HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
FormidableLabs
rapscallion
JavaScript2017–2018
FormidableLabs / rapscallion · Archived

rapscallion

Asynchronous React VirtualDOM renderer for SSR.

Web DevelopmentSystems & InfrastructureCreative & Media
Explore on GitHubRead Hacker News discussions
2Distinct people
4Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Asynchronous React VirtualDOM renderer for SSR.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2017-03-15 20:15:55 UTC to 2018-03-25 20:15:04 UTC.

0122017-03-01 00:00:00 UTC to 2017-04-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsMar 20172017-04-01 00:00:00 UTC to 2017-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-01 00:00:00 UTC to 2017-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-01 00:00:00 UTC to 2017-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-07-01 00:00:00 UTC to 2017-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 00:00:00 UTC to 2017-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-01 00:00:00 UTC to 2017-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 20172017-10-01 00:00:00 UTC to 2017-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-01 00:00:00 UTC to 2017-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2018-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-01 00:00:00 UTC to 2018-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-01 00:00:00 UTC to 2018-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20172017-03-01 00:00:00 UTC2017-04-01 00:00:00 UTC211
Apr 20172017-04-01 00:00:00 UTC2017-05-01 00:00:00 UTC000
May 20172017-05-01 00:00:00 UTC2017-06-01 00:00:00 UTC000
Jun 20172017-06-01 00:00:00 UTC2017-07-01 00:00:00 UTC101
Jul 20172017-07-01 00:00:00 UTC2017-08-01 00:00:00 UTC000
Aug 20172017-08-01 00:00:00 UTC2017-09-01 00:00:00 UTC000
Sep 20172017-09-01 00:00:00 UTC2017-10-01 00:00:00 UTC000
Oct 20172017-10-01 00:00:00 UTC2017-11-01 00:00:00 UTC000
Nov 20172017-11-01 00:00:00 UTC2017-12-01 00:00:00 UTC000
Dec 20172017-12-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
Jan 20182018-01-01 00:00:00 UTC2018-02-01 00:00:00 UTC000
Feb 20182018-02-01 00:00:00 UTC2018-03-01 00:00:00 UTC000
Mar 20182018-03-01 00:00:00 UTC2018-04-01 00:00:00 UTC101

What Hacker News says

4 sources
migueloller·Mar 25, 2018
> SSR throughput of your server is significantly less than CSR throughput. For react in particular, the throughput impact is extremely large. ReactDOMServer.renderToString is a synchronous CPU bound call, which holds the event loop, which means the server will not be able to process any other request till ReactDOMServer.renderToString completes. Let’s say that it takes you 500ms to SSR your page, that means you can at most do at most 2 requests per second. BIG CONSIDERATION If your `renderToString` is taking 500ms you should really consider using `renderToNodeStream` [1]. It will significantly reduce TTFB and runs asynchronously, letting your Node.js server handle more incoming requests. This [2] blog post goes into more detail. Also, if you don't want to use streams, Rapscallion [3] provides an asynchronous alternative to `renderToString
Read the rest
`. [1] https://reactjs.org/docs/react-dom-server.html#rendertonodes... [2] https://zeit.co/blog/streaming-server-rendering-at-spectrum [3] https://github.com/FormidableLabs/rapscallion
In The Benefits of Server Side Rendering Over Client Side Rendering
divmain·Jun 9, 2017
I attended Code Fellows in October-December of 2013. I had held a handful of tech-heavy positions prior to that time, but had never worked as a software engineer/developer. I originally saw three primary benefits to attending bootcamp, and I think they're still relevant: 1. It gave me some credibility. Before bootcamp, I had worked with children overseas for a couple of years, and as a care provider the year before that. I had considerable tech experience further back, but nothing related to software development. My resume would have been easy to discard without some way to get connected with employers. 2. It enhanced my motivation. I was paying a lot of money out of pocket, so it placed pressure on me to follow through. I also enjoy working with people, and the classroom setting exceeded self-study in a number of ways. 3. It provid
Read the rest
ed people I could go to when I was stuck. This only happened a half dozen times over the course of the program, but any one of these times might've derailed my interest or motivation. Overall, my experience was very positive and I was offered a position at Formidable Labs (now just Formidable) before graduating. It has gone rather well since then. I started as a junior engineer on their Walmart project and progressed to a senior position on my team within the year. A few months in, I received a ~30% raise. From there, I joined the Walmart Core Web team. That involved building foundational libraries, components, and patterns for the rest of the web teams, as well as a lot of broad architectural work. After a couple of months on that team and some significant successes, I took on additional responsibility, which coincided with another ~35% raise. Since then, I've worked on Formidable projects for Microsoft and Starbucks, in senior and lead roles. Starting Monday, I'm joining the Edge browser team at Microsoft as a program manager. Its hard to know what I should attribute my success to - I definitely went into bootcamp with the intention to make the most of every opportunity that came my way, and I continued in that mindset afterwards. I jumped at every chance to learn something new, and spent considerable amounts of time outside of work learning and doing OSS. A few of my projects [0][1][2] got relatively popular (others, not so much [3][4]). All of these were side projects that I pursued independantly, and I think that increased my desireability as a team member. A lot of it was probably timing and luck too! It's worth noting, however, that my experience was atypical and not in line with the rest of my cohort. I know at least a handful that struggled to find positions. [0] github.com/divmain/GitSavvy [1] github.com/FormidableLabs/rapscallion [2] github.com/FormidableLabs/freactal [3] interlockjs.com [4] github.com/divmain/recollect
In Ask HN: People who completed a bootcamp 3+ years ago: what are you doing now?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.