On Friday, August 26, 2016 at 9:38:23 PM UTC+1, Nick H wrote: > > So I agree that Cmd itself is not suitable for this more complex version > of the queue problem. But that's fine. If you feel that the way Elm is > being presented, that it is encouraging (or pressuring?) us to solve every > problem with commands, then maybe we need to change the text of the > guide/documentation/website. > Newbie's opinion here, hopefully this can steer the discussion in a helpful way.
In Elm tutorial you can read this: In Elm, commands (Cmd) are how we tell the runtime to execute things that > involve side effects. This caused me to look into Cmd as a first reaction when trying to build something where a child had to communicate state changes through websockets (only present in the parent). I hit a rubber wall and only found a good way of handing the situation when Josh pointed me to the "OutMsg pattern" he used. As a newbie, I struggle to grasp whether I should tap into the Cmd module, and if so, how to do that. -- 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.
