From 80d3591c7c6aad8e3d610a36ab60248d941ce898 Mon Sep 17 00:00:00 2001 From: petehunt Date: Tue, 4 Jun 2013 13:09:20 -0700 Subject: [PATCH] Bring in the last few edits --- _posts/2013-06-04-why-react.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/_posts/2013-06-04-why-react.md b/_posts/2013-06-04-why-react.md index 2ea0f5f7..4ec633ab 100644 --- a/_posts/2013-06-04-why-react.md +++ b/_posts/2013-06-04-why-react.md @@ -37,8 +37,8 @@ React really shines when your data changes over time. In a traditional JavaScript application, you need to look at what data changed and imperatively make changes to the DOM to keep it up-to-date. Even AngularJS, -which provides a declarative interface via directives and data binding requires -a linking function to manually update DOM nodes. +which provides a declarative interface via directives and data binding [requires +a linking function to manually update DOM nodes](http://docs.angularjs.org/guide/directive#reasonsbehindthecompilelinkseparation). React takes a different approach. @@ -70,7 +70,8 @@ some pretty cool things with it: - Facebook has dynamic charts that render to `` instead of HTML. - Instagram is a "single page" web app built entirely with React and `Backbone.Router`. Designers regularly contribute React code with JSX. -- We've built an internal prototype that runs React apps in a web worker. +- We've built internal prototypes that run React apps in a web worker and use + React to drive **native iOS views** via an Objective-C bridge. - You can run React [on the server](http://github.com/petehunt/react-server-rendering) for SEO, performance, code sharing and overall flexibility.