This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-13
Channels
- # aleph (1)
- # announcements (18)
- # babashka (11)
- # beginners (112)
- # business (1)
- # calva (19)
- # cider (8)
- # clj-kondo (63)
- # cljsrn (10)
- # clojure (188)
- # clojure-australia (1)
- # clojure-dev (38)
- # clojure-europe (112)
- # clojure-nl (3)
- # clojure-provo (1)
- # clojure-spec (22)
- # clojure-uk (108)
- # clojurescript (37)
- # cryogen (4)
- # cursive (8)
- # data-science (1)
- # datomic (13)
- # emacs (9)
- # events (1)
- # fulcro (26)
- # funcool (3)
- # graalvm (2)
- # graphql (11)
- # helix (8)
- # jobs (1)
- # jobs-discuss (7)
- # nrepl (3)
- # off-topic (72)
- # pathom (10)
- # pedestal (1)
- # reagent (6)
- # reitit (7)
- # remote-jobs (1)
- # shadow-cljs (28)
- # xtdb (12)
If this helps anyone, I wrote an adapter to treat a java.util.concurrent.SubmissionPublisher as a Manifold sink: https://gist.github.com/KingMob/149e1b21674c9b027699753143878ab8 I ended up choosing to use Websockets in the end, but I did successfully use this for a few weeks. (The reason I switched is the whole http://reactive-streams.org / Java Flow design is more like a complicated, pull-based lazy sequence, while most reactive patterns, including Manifold, are more like blockable chains of dominos. I understand the stated goals of http://reactive-streams.org, I just don't think the result very stream-like)