4 ms·

EDIT: not true. see below. ---------------------------- Good call! Benchmark 1 is about 33x faster in my browser (with the setTimeout fallback being used, I t

by drfloob 13y ago

EDIT: not true. see below. ---------------------------- Good call! Benchmark 1 is about 33x faster in my browser (with the setTimeout fallback being used, I think).~ http://drfloob.github.io/todomvc/labs/architecture-examples/react-raf/ http://drfloob.github.io/todomvc/labs/architecture-examples/... This is the same React TodoMVC example with a different `react-with-addons.js`, built using React v0.9.0 and https://github.com/petehunt/react-raf-batching https://github.com/petehunt/react-raf-batching.

swannodette 13y ago
The timings you are presenting in the UI are not accurate. But you are correct that this approach results in timings that are almost identical to Om. Use the Chrome Dev Tools profiler flamegraph if you want to confirm what I'm saying.
- drfloob 13y ago
  Ah, right. Benchmark 1 is actually ~350ms on my machine. Thanks for the lesson in profiling asynchronous code. I revisited the React+_tree benchmark claims, too, and I think they are still spot on. If you're interested at all, I'd appreciate you taking the time to check my work there.
  - swannodette 13y ago
    I took a look but it's hard to judge since you are using React 0.8.0 and Om is now on React 0.9.0.