status-im/re-frame
2
0
Fork 0
mirror of https://github.com/status-im/re-frame.git synced 2025-02-22 14:58:12 +00:00
Code Issues Projects Releases Wiki Activity

More readme tweaks

Browse Source
This commit is contained in:
mike-thompson-day8 2015-07-15 16:22:37 +10:00
parent d97e994d9f
commit 328c3e0dca
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -72,9 +72,6 @@ __Warning__: That was the summary. What follows is a long-ish tutorial/explanat
- [What Problem Does It Solve?](#what-problem-does-it-solve)
- [Correct Acronym?](#correct-acronym)
- [Mostly A Mashup](#mostly-a-mashup)
- [Client Side Bias](#client-side-bias)
- [Guiding Philosophy](#guiding-philosophy)
- [FRP Clarifications](#frp-clarifications)
- [Explaining re-frame](#explaining-re-frame)
@ -116,12 +113,12 @@ For all its considerable brilliance, Reagent (+ ReactJS)
delivers only the 'V' part of a traditional MVC framework.
But apps involve much more than V. Where
does the control logic go? How is state stored & manipulated, how does the V bit source data? etc.
does the control logic go? How is state stored & manipulated? etc.
We read up on [Flux], [Pedestal App],
[Hoplon], [OM], [Elm], etc and re-frame is what emerged.
[Hoplon], [OM], [Elm], etc and re-frame is the architecture that emerged.
So re-frame ended up with M, V, and C parts but they aren't objects, they
re-frame does have M, V, and C parts but they aren't objects, they
are pure functions (or pure data),
and they are wired together via reactive data flows. It is sufficiently different in nature
from (traditional, Smalltalk) MVC that calling it MVC would be confusing. I'd