From 01ac4e13d3ed67fd65e09a3eaa2d4a5cb080fe7b Mon Sep 17 00:00:00 2001 From: Travis CI Date: Tue, 29 Mar 2016 21:26:34 +0000 Subject: [PATCH] Rebuild website --- docs/interactivity-and-dynamic-uis.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/interactivity-and-dynamic-uis.html b/docs/interactivity-and-dynamic-uis.html index 9842ed1fc7..702aaa97b0 100644 --- a/docs/interactivity-and-dynamic-uis.html +++ b/docs/interactivity-and-dynamic-uis.html @@ -443,7 +443,7 @@

Under the Hood: Autobinding and Event Delegation #

Under the hood, React does a few things to keep your code performant and easy to understand.

-

Autobinding: When creating callbacks in JavaScript, you usually need to explicitly bind a method to its instance such that the value of this is correct. With React, every method is automatically bound to its component instance (except when using ES6 class syntax). React caches the bound method such that it's extremely CPU and memory efficient. It's also less typing!

+

Autobinding: When creating callbacks in JavaScript, you usually need to explicitly bind a method to its instance such that the value of this is correct. With React, every method is automatically bound to its component instance (except when using ES6 class syntax). React caches the bound method such that it's extremely CPU and memory efficient. It's also less typing!

Event delegation: React doesn't actually attach event handlers to the nodes themselves. When React starts up, it starts listening for all events at the top level using a single event listener. When a component is mounted or unmounted, the event handlers are simply added or removed from an internal mapping. When an event occurs, React knows how to dispatch it using this mapping. When there are no event handlers left in the mapping, React's event handlers are simple no-ops. To learn more about why this is fast, see David Walsh's excellent blog post.

Components are Just State Machines #