This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-06
Channels
- # announcements (2)
- # architecture (2)
- # aws (18)
- # babashka (7)
- # beginners (149)
- # bristol-clojurians (4)
- # calva (11)
- # chlorine-clover (1)
- # cider (8)
- # clj-kondo (2)
- # cljdoc (2)
- # cljsrn (2)
- # clojure (186)
- # clojure-canada (3)
- # clojure-europe (3)
- # clojure-gamedev (5)
- # clojure-italy (1)
- # clojure-nl (13)
- # clojure-norway (4)
- # clojure-spec (25)
- # clojure-uk (32)
- # clojurescript (75)
- # core-async (2)
- # cursive (16)
- # data-science (3)
- # datomic (20)
- # docker (1)
- # emacs (26)
- # fulcro (7)
- # graphql (1)
- # incanter (1)
- # leiningen (1)
- # luminus (7)
- # malli (7)
- # mount (11)
- # off-topic (19)
- # pathom (15)
- # re-frame (9)
- # reagent (9)
- # remote-jobs (4)
- # ring-swagger (4)
- # shadow-cljs (63)
- # spacemacs (11)
- # sql (2)
- # vscode (7)
@richard are we ready to start promoting Async in Clojure as next week's topic? For me alternative CSP implementations sound really interesting (re:meetup suggestions)
:thinking_face: I thought we were going to look at Clojure / Python interop with https://github.com/cnuernber/libpython-clj because of Carin Meier's blog post - https://gigasquidsoftware.com/blog/2020/01/10/hugging-face-gpt-with-clojure/ 🤐 But we did discuss a lot of options. What alternative CSP implementations were you thinking?
Were you thinking of trying Maciej's await-cps? https://github.com/mszajna/await-cps
yeah I did forget to put the suggestion on http://meetup.com: https://www.meetup.com/Bristol-Clojurians/events/hdzjnrybcdbqb/ which is where the CSP suggestion is, I think if we have one topic per session we do need to pick one for next session then queue the rest