From 328c3e0dcaae202734ee3b7d8fcca7d4811b8863 Mon Sep 17 00:00:00 2001 From: mike-thompson-day8 Date: Wed, 15 Jul 2015 16:22:37 +1000 Subject: [PATCH] More readme tweaks --- README.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 3c766ff..5ef3248 100644 --- a/README.md +++ b/README.md @@ -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