From 12c546924cf57d1a10f2e0198d6f7f21bffe2427 Mon Sep 17 00:00:00 2001 From: nickolasgregory Date: Mon, 15 Sep 2014 19:54:02 +1000 Subject: [PATCH] Update practices.md --- docs/practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/practices.md b/docs/practices.md index 375372cd..996cac9c 100644 --- a/docs/practices.md +++ b/docs/practices.md @@ -95,7 +95,7 @@ In the unlikely case that you have another global variable called `m` in your pa Calling this method while using `m.module` or `m.route` should only be done if you have recurring asynchronous view updates (i.e. something that uses setInterval). -If you're integrating other non-recurring services (e.g. calling setTimeout), you should use [`m.startComputation` / `m.emdComputation`](mithril.computation.md) instead. +If you're integrating other non-recurring services (e.g. calling setTimeout), you should use [`m.startComputation` / `m.endComputation`](mithril.computation.md) instead. This is the most potentially expensive method in Mithril and should not be used at a rate faster than the rate at which the native `requestAnimationFrame` method fires (i.e. the rate at which browsers are comfortable calling recurring rendering-intensive code). Typically, this rate is around 60 calls per second.