Fork me on GitHub
#ldnclj
<
2015-11-03
>
pupeno07:11:24

Good morning.

thomas08:11:54

Guten Morgen

jonpither12:11:40

afternoon, from Copenhagen

mccraigmccraig12:11:35

god dag jonpither i københavn

jonpither12:11:23

god dag indeed

xlevus12:11:05

you like dags?

mccraigmccraig12:11:48

more than nats anyway

jonpither13:11:55

Anyone using promesa over core.async?

mccraigmccraig13:11:16

@jonpither: i'm using funcool/cats mlet/alet to manage my async processing in both cljs+clj ... (not with promesa in cljs, but one-shot core.async channels, but not dissimilar to promesa in the end)

jonpither13:11:36

you got any example code you could lead me?

jonpither13:11:20

I was thinking of making a case for a client to replace promesa + funcool cats with core.async, but that google group post gave me pause for thought

malcolmsparks23:11:17

I'm not very familiar with promesa, but there seems to be parallels between promesa's mlet and @ztellman manifold's let-flow. Also between es7's Promise.all, promesa's promise chaining and manifold's d/chains. But the Tim Baldridge quote in the clojurescript list thread about 'one-shot' channels rings true.

malcolmsparks23:11:53

I'm still somewhat enamored by manifold and not sure whether it's better than core.async or not. I don't think it's helpful to say one is 'better', they are too different. Right now I prefer manifold though.

malcolmsparks23:11:49

The try/catch error handling turns out to be important in my use-cases. I think it's just a matter of deciding which async tool is best of a particular situation but not being afraid to try different things