The library for web and native user interfaces.
Bring in the last few edits
petehunt committed
Jun 4, 2013 at 13:09 UTC
4201ddaf4ef738eb4fb60e940d8af3e061d35b91
1 file changed
+4
-3
docs/_posts/2013-06-04-why-react.md
+4
-3
@@ -37,8 +37,8 @@ React really shines when your data changes over time.
37
38
In a traditional JavaScript application, you need to look at what data changed
39
and imperatively make changes to the DOM to keep it up-to-date. Even AngularJS,
40
-which provides a declarative interface via directives and data binding requires
41
-a linking function to manually update DOM nodes.
40
+which provides a declarative interface via directives and data binding [requires
41
+a linking function to manually update DOM nodes](http://docs.angularjs.org/guide/directive#reasonsbehindthecompilelinkseparation).
42
43
React takes a different approach.
44
@@ -70,7 +70,8 @@ some pretty cool things with it:
70
- Facebook has dynamic charts that render to `<canvas>` instead of HTML.
71
- Instagram is a "single page" web app built entirely with React and
72
`Backbone.Router`. Designers regularly contribute React code with JSX.
73
-- We've built an internal prototype that runs React apps in a web worker.
73
+- We've built internal prototypes that run React apps in a web worker and use
74
+ React to drive **native iOS views** via an Objective-C bridge.
75
- You can run React
76
[on the server](http://github.com/petehunt/react-server-rendering)
77
for SEO, performance, code sharing and overall flexibility.