> On Sep 10, 2016, at 1:22 AM, Peter Damoc <[email protected]> wrote: > > Charlie was right, an accordion is a better example.
I'm sure it is. As is a date picker. As with lists of counters as models in the Elm Architecture documents, my example is entirely contrived — hence, my subject line — with the intent that in being so contrived and yet so simple, attention could instead focus on the proposed pattern for handling a combination of public/shared state and private/local state. I figured that these discussions had come around enough that that context would be as clear as the context for why a list of counters is interesting. I seem to have been wrong in that regard. > From my view, the issue here is with how you scale a page when it is full of > such "components". I rather hoped that if the approach I took could be endorsed as being closer to what some would argue is the right way to write Elm code that the scalability issue could be the next discussion point. But to get there we need something that's being scaled and we can't even seem to get to that point. Mark -- 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.
