Updates take CPU time, heat up your user's laptop, reinvigorate cold memory, often when your user is trying to use their computer for other things. If running some code won't be useful, you should avoid running it. It also saves the environment just a tiny amount.
On Monday, July 17, 2017 at 6:03:03 AM UTC-7, John Bugner wrote: > > The signature of program.subs (from > http://package.elm-lang.org/packages/elm-lang/core/5.1.1/Platform ) is: > 'model -> Sub msg'. > > Why isn't it just 'Sub msg' ? What's the point of including the model in > there? Sure, it lets you control what subscriptions you listen too > depending on the current model, but what's the benefit of that? Is it wise > to rely on this function to control what messages you receive? The update > function still has to have a case for every message no matter the state, > after all. Is there some performance improvement from using this that I'm > not aware of? > > -- 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.
