Skip to content
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

New marketing copy #440

Merged
merged 5 commits into from
Dec 1, 2013
Merged

New marketing copy #440

merged 5 commits into from
Dec 1, 2013

Conversation

petehunt
Copy link
Contributor

I think that our 3 bullet points are pretty meaningless right now since they don't differentiate React from alternatives. Even if we are more declarative and more efficient and more flexible it says nothing about how we're different.

So I changed these. The goal is for someone to read these and instantly be able to differentiate React from alternatives.

React computes the minimal set of changes necessary to keep your DOM
up-to-date.
React uses a virtual DOM representation for ultra-high performance. It can also
run outside of the browser on Node.js.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe we should specifically use the phrase "server-side rendering" here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It can also render on the server using Node.js.

?

@krsmedlund
Copy link

there is a typo in the text at <i>virtual DOM</li>

@petehunt
Copy link
Contributor Author

petehunt commented Nov 4, 2013

ping

@vjeux
Copy link
Contributor

vjeux commented Nov 4, 2013

@vjeux approved

React uses a declarative paradigm that makes it easier to reason about
your application.
React isn&apos;t the first JS library to let you build components. But it&apos;s
the only one that emphasizes building components out of other components above all else.
Copy link
Collaborator

Choose a reason for hiding this comment

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

But it's the only one that emphasizes building components out of other components above all else.

This sounds to me like we're sacrificing other things to make components easier (which I don't think is true?). Maybe:

But with a focus on composability, React makes it simple to keep each part of your app self-contained.

(also rsquo not apos?)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Really struggling with this. tbh, I liked the old one better but it was really aggressive. Any ideas?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Well, I think it's okay to be super aggressive in claims like this if it's true… but I'm not sure that the advantage you claim is even concrete enough to understand. What do you think of:

"By making it easy to compose components, React let you to make your views more modular, making them easier to maintain."

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 draw a distinction between techniques like Angular's transclusion which requires massging your data into and out of the DOM to use composition and react-style composition.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah, I know what you mean but I don't think it'll be as obvious to most visitors.

petehunt added a commit that referenced this pull request Dec 1, 2013
@petehunt petehunt merged commit 285e3a8 into facebook:master Dec 1, 2013
sophiebits added a commit to sophiebits/react that referenced this pull request Dec 2, 2013
Most significant change is updating the leading copy to match facebook#440.
@sophiebits sophiebits mentioned this pull request Dec 2, 2013
zpao pushed a commit that referenced this pull request Dec 2, 2013
Most significant change is updating the leading copy to match #440.
petehunt added a commit that referenced this pull request Dec 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants