I've been determined to try to use Elm as a solution for building potentially large applications. Maybe I should just be taking what you are saying as an indication that it's not useful for that and I should go back to looking at JavaScript. I'd hate to do that because I like the typed, pure functional approach but you seem insistent that the right approach to Elm is to write relatively monolithic pieces of code and then try to tease them apart if they become too complex. People create layer cake designs because they help manage systems complexity. What I'm hearing here is that Elm should only be considered for the very topmost layer. If it can't reach deeper, then it needs to compete with the technologies that sit below it because those will try to push upward.
My example here was contrived in an effort to keep things focused on the design issue. You dismiss this as inventing a problem to solve. The problem I'm trying to solve is answering the question of whether Elm can be useful in building a large, complex application and if so how one should go about doing so since OO design patterns generally don't apply. If you want to tell me that Elm isn't useful for that and it's really just for hacking out a more reliable front end with the back end all coded in something else then I will take that advice seriously and start looking elsewhere for useful technologies. Mark On Fri, Aug 26, 2016 at 10:42 AM, Richard Feldman < [email protected]> wrote: > I'm going to try to take the large app design questions and focus them on >> a more narrow and *admittedly contrived example*. >> >> From what I understand of effect managers, we could write an effect >> manager to do this but *the documentation around effect managers >> discourages reaching for them as a solution*. >> > >> *It feels like it gets at the sort of problem for which there ought to be >> a design pattern* — i.e., structure your types and functions like this >> to solve this sort of problem. >> > > You seem very determined to invent a problem to solve, and then to ask the > community for assistance solving it. My repeatedly pointing this out in > other threads has obviously not dissuaded you. > > Maybe that's fun for you, but I would hate to see a beginner read this > post and think "maybe I need custom effect managers to write a scalable Elm > application," which is *insane*. > > Anyway, carry on - I just want to make it clear to anyone reading this > thread that this is just the OP creating puzzles to solve. If anyone > reading this is wondering whether it applies to you, don't worry: it > doesn't. > > -- > 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. > -- 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.
