On Tuesday, 11 February 2014 02:24:22 UTC+11, Joel wrote: > It seems the benefits of FRP are negated when using a render() method. If I > just calculate what I need at render time, not sure how I would leverage an > FRP lib. I didn't realize one might "cancel" the other, but isn't that the > case? > > J
My simplified take on this: I see them as distinct approaches. Both are good. FRP tracks small changes in models (and possibly chains of calculations) and when it detects a change, it then updates only what differs. Om/React - calculates a complete new state and then calculates what changed (rather than tracking/inferring it). It then updates what only what differs. This is not to say that both could not be used in an app - if there was a case for this - but that they would not be used on the same parts. also: The assumption of Om/React is that the diff can be calculated fast enough that it does not matter to the UI/user. In some cases it might. The challenge for FRP is that the chains of change are explicitly specified/managed which may add to maintenance/change effort. D -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
