On Wed, Apr 19, 2017 at 2:58 AM, Richard Feldman < [email protected]> wrote: > > "Everything ought to have the same API" is a much harder claim to defend. > It sounds wrong at face value, and I haven't seen any evidence (in this > thread or elsewhere) to convince me that it's a wise goal to pursue. :) >
But isn't the entirety of the html package and actual example of an unified API? All the widgets there have the same API: widget : List (Attribute msg) -> List (Html msg) -> Html msg checkbox : (Bool -> msg) -> Bool -> Html msg How about the case where one has calls to a server involved? for example a weather widget or some kind of "Quote of the day" widget, a stocks ticker, etc. How does one handles side-effects (http, random, time etc) with this pattern? -- 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.
