This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-06
Channels
- # adventofcode (24)
- # aleph (1)
- # bangalore-clj (2)
- # beginners (196)
- # boot (148)
- # cider (18)
- # clara (83)
- # cljsrn (24)
- # clojure (210)
- # clojure-brasil (3)
- # clojure-china (1)
- # clojure-italy (11)
- # clojure-korea (8)
- # clojure-russia (82)
- # clojure-spec (115)
- # clojure-uk (130)
- # clojurescript (109)
- # core-async (7)
- # cryogen (1)
- # cursive (22)
- # datascript (11)
- # datomic (6)
- # devcards (2)
- # emacs (1)
- # garden (1)
- # hoplon (2)
- # incanter (1)
- # klipse (4)
- # luminus (4)
- # off-topic (89)
- # om (53)
- # onyx (78)
- # parinfer (9)
- # proton (3)
- # protorepl (20)
- # re-frame (107)
- # reagent (52)
- # rum (30)
- # spacemacs (1)
- # testing (3)
- # untangled (31)
- # vim (43)
- # yada (9)
hi all, I’m not sure how to google for this question - I understand why you might want to use a buffered channel in multithreaded java world. But in js, is there ever any reason to use a buffer bigger than 1?
I can’t quite wrap my brain around a buffered channels in cljs, does anyone know of good blog posts about this?
regarding mult … I get odd behaviours if I create a mult inside a function and then use it in a go loop; if I def a mult, all goes well - is this a known pattern?
@hiredman, I get it now, thanks. Not sure what I was thinking before. Actually I was thinking along the lines of in single thread if both producer and consumer run on every tick of the loop, then why would I ever need buffers?! But yeah, senior moment or something, because now I realize there can be tons of ajax requests or something that you want to queue up. duh!