-
Notifications
You must be signed in to change notification settings - Fork 46.5k
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
Remove "V in MVC" text from the website #3776
Comments
👍 |
cc @petehunt who also wants it gone |
👍 |
3 similar comments
+1 |
👍 |
👍 |
I know it's entirely anecdotal, but here is my story:
Anyway, now that I fully understand React, I can understand why that sentence is arguably a bit misleading, but I also see how it succinctly communicates what React actually does in terms that were very familiar to me. |
I think it would be prudent to add
instead. It implies that React can be used on its own but can also be a view in other frameworks while being succinct. |
How about something like
|
Oh wait, @ryanflorence already said that better. I missed that in his initial comment. |
@jimfb really succinctly said what I've found really helpful about the line as it is. it's terse and clear, and used analogy I already understood well. Sure it's technically misleading if you already understand react, but I found it really helpful as a newcomer. Which is more to the point that the tag line is for people who don't know React, but likely do all know about views in MVC's |
I'm kind of ambivalent about it. I'd like to have it phrased in a way that keeps the original “just the UI” meaning but also suggests React is better off without MC baggage. |
Something has to replace the MC though. Whether it's Flux, Relay or another system entirely. The default option of callbacks passed down 4+ levels deep as props (as you get if you extrapolate from Thinking in React) becomes quickly unmanageable. Maybe take @ryanflorence's suggestion, and also add to the "Data Flow" bullet point:
This way, we still explain how it relates to MVC and present a recommended architecture. |
No comments for over six months. It isn't clear that we want to change this, so the bug isn't actionable. This might get changed/fixed as part of a bigger docs rework, but let's close for now. |
Going with #7012. |
I'm sure there was some thought put into this phrase on the website, but I think it breeds the idea that you just dump
React.render
inside of aBackbone.View.render
as though its a recommended application architecture. In my experience, people end up with all the same problems they had before react: incomprehensible webs of events, cascading updates, etc.Perhaps something like:
The text was updated successfully, but these errors were encountered: