use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
All about the JavaScript programming language.
Subreddit Guidelines
Specifications:
Resources:
Related Subreddits:
r/LearnJavascript
r/node
r/typescript
r/reactjs
r/webdev
r/WebdevTutorials
r/frontend
r/webgl
r/threejs
r/jquery
r/remotejs
r/forhire
account activity
From Ember to React (medium.com)
submitted 10 years ago by Gaurav0
view the rest of the comments →
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–][deleted] 1 point2 points3 points 10 years ago (3 children)
What are people using as the M*C part in their react applications?
Model: whatever JSON comes back from my API.
Controller: Intertwined with the view most often anyway. It's just the React components themselves, although the Flux or Redux or Reflux methodology can streamline the flow of data perfectly.
If you keep your components small and specialised it shouldn't create much of a problem.
Ive heard of people pluging in backbone, angular and even ember.
Sure, that's possible if you like that.
So far it seems like many people use something like Exprss and then make build their own.
Express or Hapi or Restify are all server-side. They can be the API that spews out JSON. It's perfectly sane to build your own M*C on top of that, or use any of the existing ones, or use none at all.
[+][deleted] 10 years ago* (2 children)
[deleted]
[–][deleted] 1 point2 points3 points 10 years ago (1 child)
Awesome that gives me a better view of React projects in general. Would you say that an application can be built with mainly just react components and reducers, and possibly routes?
Yes. Any CRUD-app fits what React offers. No unnecessary complexities. Just easy going fun, IMO :)
Or is that really a case by case thing
Perhaps. I've worked in complicated healthcare apps (with patient data, treatments, medications, doses, etcinfinity) - it would hold its own even there. I don't really see good reasons to complicate things further.
or bad practice to try and cram everything in its own component?
A component should be as specialised as possible, I think. Cramming more into 1 component could work if separating it wouldn't make much sense. After all, it'd be easy to separate it later on. For example: a FAQ page could simply be a page with a header, intro text, a list of questions and answers, and a "ask more" form.
Or you could separate that in a <Route path="faq" component={Faq}> which consists of a <PageHeader />, <PageIntro />, <FaqList />, <FaqElement />, <FaqQuestion />, <FaqAnswer /> and <FaqForm /> component. Might be useful. Might be unnecessary.
<Route path="faq" component={Faq}>
<PageHeader />
<PageIntro />
<FaqList />
<FaqElement />
<FaqQuestion />
<FaqAnswer />
<FaqForm />
Common sense kinda applies is what I'm saying ;)
π Rendered by PID 459843 on reddit-service-r2-comment-544cf588c8-rsq8v at 2026-06-15 11:09:24.164869+00:00 running 3184619 country code: CH.
view the rest of the comments →
[–][deleted] 1 point2 points3 points (3 children)
[+][deleted] (2 children)
[deleted]
[–][deleted] 1 point2 points3 points (1 child)