jarrad

$> brew cask install java

$> brew install kafka

$> vim ~/bin/kafka
# ~/bin/kafka
#!/bin/bash

zkServer start
kafka-server-start.sh /usr/local/etc/kafka/server.properties

teocomi

# =============== #
# Unity generated #
# =============== #
[Tt]emp/
[Oo]bj/
[Bb]uild
/[Bb]uilds/
/[Ll]ibrary/
sysinfo.txt
*.stackdump

fokusferit

Shallow

Real unit test (isolation, no children render)

Simple shallow

Calls:

• constructor
• render

axemclion

import MessageQueue from 'react-native/Libraries/BatchedBridge/MessageQueue.js';

const WHITELIST = ['UIManager'];
const NOOP = () => { };

let queue = [];
let now = 0;
export default {
  start() {
    MessageQueue.spy(msg => {

acdlite

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?