ldnclj

Find us on #clojure-uk
pupeno 2015-11-03T07:44:24.000643Z

Good morning.

maleghast 2015-11-03T08:45:36.000644Z

Hello @pupeno

thomas 2015-11-03T08:47:54.000645Z

Guten Morgen

agile_geek 2015-11-03T10:07:32.000646Z

Yo!

jonpither 2015-11-03T12:08:40.000647Z

afternoon, from Copenhagen

mccraigmccraig 2015-11-03T12:22:35.000648Z

god dag jonpither i københavn

jonpither 2015-11-03T12:23:23.000649Z

god dag indeed

xlevus 2015-11-03T12:28:05.000650Z

you like dags?

mccraigmccraig 2015-11-03T12:29:48.000651Z

more than nats anyway

jonpither 2015-11-03T13:09:55.000652Z

Anyone using promesa over core.async?

jonpither 2015-11-03T13:29:49.000653Z

This is interesting reading on the above: https://groups.google.com/forum/#!topic/clojurescript/LBy0yiZiWrA

mccraigmccraig 2015-11-03T13:46:16.000654Z

@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)

jonpither 2015-11-03T13:48:30.000655Z

ha

jonpither 2015-11-03T13:48:36.000656Z

you got any example code you could lead me?

mccraigmccraig 2015-11-03T13:50:02.000657Z

sure, hold on

jonpither 2015-11-03T13:52:20.000658Z

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

malcolmsparks 2015-11-03T23:41:17.000660Z

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.

malcolmsparks 2015-11-03T23:42:53.000662Z

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.

malcolmsparks 2015-11-03T23:44:49.000663Z

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