This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-03
Channels
- # admin-announcements (7)
- # beginners (30)
- # boot (181)
- # cbus (1)
- # cider (55)
- # cljs-dev (8)
- # clojure (104)
- # clojure-dev (3)
- # clojure-japan (1)
- # clojure-russia (70)
- # clojurescript (139)
- # core-logic (4)
- # cursive (23)
- # datomic (25)
- # devcards (10)
- # events (11)
- # funcool (1)
- # hoplon (39)
- # jobs (10)
- # ldnclj (19)
- # lein-figwheel (21)
- # off-topic (4)
- # om (174)
- # onyx (46)
- # re-frame (25)
- # reagent (3)
- # yada (7)
Good morning.
god dag jonpither i københavn
more than nats anyway
This is interesting reading on the above: https://groups.google.com/forum/#!topic/clojurescript/LBy0yiZiWrA
@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)
sure, hold on
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
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.
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.
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