From 04fde10bc86831e44ba414ca7cecd8a2e171f343 Mon Sep 17 00:00:00 2001 From: Tharaka Manawardhana Date: Sat, 1 Sep 2018 15:05:15 +1000 Subject: [PATCH] Update BatchingAndTiming.md --- doc/BatchingAndTiming.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/BatchingAndTiming.md b/doc/BatchingAndTiming.md index 3e9a6a0..407199a 100644 --- a/doc/BatchingAndTiming.md +++ b/doc/BatchingAndTiming.md @@ -9,7 +9,7 @@ This is good for all sorts of reasons: * The new code does proper batching of renderings even when changes to atoms are done outside of event handlers (which is great for e.g core.async users). * Repaints can be synced by the browser with for example CSS transitions, since Reagent uses requestAnimationFrame to do the batching. That makes for example animations smoother. -In short, Reagent renders less often, but at the right times. For a much better description of why async rendering is good, see David Nolen’s [excellent explanation here.](http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs/) +In short, Reagent renders less often, but at the right times. For a much better description of why async rendering is good, see David Nolen’s [excellent explanation here.](http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs) ## The bad news