Skip to content

Instantly share code, notes, and snippets.

View erabhimanyu's full-sized avatar
🍁
Perceive. Grow. Disrupt

Abhimanyu Arora erabhimanyu

🍁
Perceive. Grow. Disrupt
View GitHub Profile
@kylefurlong
kylefurlong / errno
Last active July 22, 2019 18:38
errno cli
function errno() { (grep "^$1 " ~/errno.db || cat ~/errno.db) }
@acdlite
acdlite / coordinating-async-react.md
Last active June 17, 2024 11:56
Demo: Coordinating async React with non-React views

Demo: Coordinating async React with non-React views

tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.

A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.

But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.

How do we solve this with React?

@radosny
radosny / LLNODE.md
Last active May 20, 2019 02:49
Node postmortem debugging (OSX)

Node postmortem debugging (OSX)

I assume that you have an access to ssh and node server process is up and running.

1. Taking core dump

To get core dump of running node process:

  • Take PID of that process:
    pgrep -lf node