Skip to content

New marketing copy #440

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Dec 1, 2013
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 11 additions & 9 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,23 +7,25 @@ id: home
<section class="light home-section">
<div class="marketing-row">
<div class="marketing-col">
<h3>Declarative</h3>
<h3>Just the UI</h3>
<p>
React uses a declarative paradigm that makes it easier to reason about
your application.
Lots of people use React as the V in MVC.
Since React makes no assumptions about the rest of your technology stack,
it&apos;s easy to try it out on a small feature in an existing project.
</p>
</div>
<div class="marketing-col">
<h3>Efficient</h3>
<h3>Virtual DOM</h3>
<p>
React computes the minimal set of changes necessary to keep your DOM
up-to-date.
React uses a <i>virtual DOM</i> diff implementation for ultra-high performance. It can also
render on the server using Node.js &mdash; no heavy browser DOM required.
</p>
</div>
<div class="marketing-col">
<h3>Flexible</h3>
<h3>Data flow</h3>
<p>
React works with the libraries and frameworks that you already know.
React implements one-way reactive data flow which reduces boilerplate and is
easier to reason about than traditional data binding.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't even know what "traditional data binding" is.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"change tracking or dirty checking the model" doesn't have the same ring to it :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, are you trying to say that a declarative render() function is easier than mutating the DOM by hand in response to changes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to say that when you use two way data binding it becomes very difficult to reason about correctness or performance issues

</p>
</div>
</div>
Expand Down Expand Up @@ -60,7 +62,7 @@ id: home
This example uses `state` to track the current list of items as well as
the text that the user has entered. Although event handlers appear to be
rendered inline, they will be collected and implemented using event
delegation.
delegation.
</p>
<div id="todoExample"></div>
</div>
Expand Down