> > So, maybe components sound too much like objects and should be avoided but > what are needed are patterns of partitioning and coordination. >
100% agree! P.S. We also need performance-oriented patterns. For example, I'm concerned > that a complex model — regardless of how it is partitioned or not — could > require many subscriptions and if these are re-computed and effects > managers are updated on every change to the model, there is likely to be a > lot of repeated busy work. Are there patterns for managing subscriptions > that avoid that? > Not at the moment, but presumably an analog to Html.lazy <http://package.elm-lang.org/packages/elm-lang/html/1.1.0/Html-Lazy> would suffice. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
