On Thu, Nov 24, 2016 at 11:17 AM, Oliver Searle-Barnes <[email protected]> wrote:
> The fact remains though that I don't feel I can offer a sound > justification as to why it's far more complicated to do these things in > Elm. Elm strives to be easy for users to understand, in this area it is > decidedly more complicated than the existing alternatives. > The class of problems you described is precisely the class of problems that Object Oriented Programming solves easily. It is the class of problems where, as a library developer, you provide and API and you allow the client to do multiple implementation of an interface, (e.g. the interface of a web-component or the interface of a debounceable app). Implementing something that solves this issue is non-trivial because it can be a source of chaos (complexity). Approaching the Expression Problem <https://en.wikipedia.org/wiki/Expression_problem> Elm chose defer solving it for later implementing only a few practical facilities like toString (allows extension of cases without recompilation) -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- 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.
