The lack of Task Ports basically lead to me putting Elm on the "watch-list" rather than actively using it on anything. Commands make it too difficult to track interdependencies between multiple separate async operations. I'm glad to see revived interest in this area, hopefully the project leadership takes interest.
On Monday, March 6, 2017 at 2:21:41 AM UTC+11, Oliver Searle-Barnes wrote: > > Having used Elm for 6 months now I'm not entirely sure why any API creates > commands rather than tasks. Wouldn't it always be beneficial to have the > option of composing rather than being forced into using an intermediate > Msg? If you don't need to compose with another task then you can always add > helpers functions to make it easy to create a command, but the opposite is > impossible. Is there a scenario where you would want the API to force > consumption as a command? > > > > On Sunday, 5 March 2017 00:21:01 UTC+1, Witold Szczerba wrote: >> >> I think that you cannot say that promises are supported by IE or are not. >> It's just that IE 11 does not provide built-in implementation of ES6 >> "Promise" interface. It does not mean you cannot use any of the >> "Promises/A+" libraries. Promises, as a concept described by "Promises/A+ >> standard specification" were widely used before any browser provided a >> default ES6 implementation. This is really a great step forward compared to >> the callback equivalent. >> >> Regards, >> Witold Szczerba >> >> On Wed, Aug 24, 2016 at 7:42 PM, Maxwell Gurewitz <maxth...@gmail.com> >> wrote: >> >>> My only comment would be that the interface should not rely on promises, >>> which are not supported by IE. Instead it should use node style callbacks. >>> >>> -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
