Add "Why React" #48
Add "Why React" #48
Conversation
|
|
||
| - **JavaScript is a flexible, powerful programming language with the ability to build abstractions.** This is incredibly important in large applications. | ||
| - "Logic" and "markup" are intimately tied, and are both part of the "presentation" layer, so we're not breaking separation of concerns. | ||
| - Large projects usually don't use WYSIWYG editors for production code |
There was a problem hiding this comment.
Not entirely sure how this motivates React. Maybe just tack on a "so…" clause to make the implication explicit?
|
Add subtitles otherwise people won't bother reading 20 paragraphs Nit: the author is being written as is, you want to put Pete Hunt |
|
Updated per your comments, what illustrations do you think we need? |
| ability to build abstractions.** This is incredibly important in | ||
| large applications. | ||
| - "Logic" and "markup" are intimately tied, and are both part of the | ||
| "presentation" layer, so we're not breaking separation of concerns. |
There was a problem hiding this comment.
so we're not breaking separation of concerns, but rather unifying the presentation layer.
|
@zpao liked it |
| large applications. | ||
| - "Logic" and "markup" are intimately tied, and are both part of the | ||
| "presentation" layer, so we're not breaking separation of concerns. | ||
| - Large projects usually don't use WYSIWYG editors for production |
There was a problem hiding this comment.
I feel like most people won't make the connection between WYSIWYG editors and splitting markup from code. I think something like:
Breaking apart markup from code is largely a historical problem. Historically, WYSIWYG editors like Dreamweaver would statically rebuild your markup each time your template changed. As a result, people would split their JS and CSS from their markup so that they could update them without rebuilding. Given that large projects don't generally use WYSIWYG editors for production code anymore, we've chosen to reduce friction by integrating rendering logic with markup.
We feel that each component should be a self contained atomic unit. In many other languages/syntaxes, you don't have separate completely disconnected files for describing presentation and behavior (think of Objective-C ViewControllers for instance).
is a bit closer to what I'd like (meh, I still hate the wording though - def. feel free to edit).
Also, fwiw, Marshall's original comment is here
There was a problem hiding this comment.
I like it, but I wish we could condense that down to a single bullet since this isn't our main point. Feel free to send a PR.
We need a way to communicate what we're actually doing rather than just how we build apps (like we do on the site.docs). This does a pretty good job of it, I think.