These are chat archives for jdubray/sam

30th
Oct 2016
Mike Nichols
@mnichols
Oct 30 2016 21:22
async
Fred Daoud
@foxdonut
Oct 30 2016 21:58
?
Fred Daoud
@foxdonut
Oct 30 2016 22:12
thanks @mnichols great to hear :)
Jean-Jacques Dubray
@metapgmr_twitter
Oct 30 2016 22:13
?
Edward Mulraney
@edmulraney
Oct 30 2016 22:30
@mnichols i couldn't agree more
Jean-Jacques Dubray
@metapgmr_twitter
Oct 30 2016 22:35
?
Mike Nichols
@mnichols
Oct 30 2016 22:50
lol sorry...i was doing a search and entered a comment I guess. If I were consistent I would have put this remark in before my entry. :laughing:
@foxdonut is there a separate discussion channel for meiosis or this it?
Mike Nichols
@mnichols
Oct 30 2016 23:29
@foxdonut never mind..I found it!
Jean-Jacques Dubray
@metapgmr_twitter
Oct 30 2016 23:44

From this new article on Elm:

Tasks are like callbacks in that instantiating them is harmless. You can instantiate a hundred Tasks that describe HTTP requests, and no network activity will happen—yet. Only once the Task is passed from function to function and handed off to the Elm runtime will it actually be performed. Tasks can be chained together like Promises, and they similarly incorporate first-class error handling; if any Task in the chain fails, the remainder of the chain is not executed, and the entire chain results in that failure value.

I am not sure that effects as data / aka managed effects are such a good model. Ultimately effects need to occur and handing off control doesn't sound that appealing (considering the main benefit is testable code).