This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-07
Channels
- # aleph (3)
- # aws (7)
- # beginners (117)
- # boot (119)
- # cider (2)
- # cljs-dev (3)
- # clojure (193)
- # clojure-austin (1)
- # clojure-dusseldorf (4)
- # clojure-finland (5)
- # clojure-france (5)
- # clojure-italy (7)
- # clojure-portugal (1)
- # clojure-russia (204)
- # clojure-serbia (5)
- # clojure-spec (31)
- # clojure-uk (64)
- # clojurescript (288)
- # community-development (9)
- # core-async (54)
- # cursive (8)
- # datascript (18)
- # datomic (26)
- # dirac (8)
- # emacs (26)
- # figwheel (1)
- # hoplon (16)
- # jobs (2)
- # jobs-discuss (4)
- # juxt (1)
- # lein-figwheel (4)
- # leiningen (14)
- # london-clojurians (2)
- # lumo (17)
- # off-topic (44)
- # om (63)
- # om-next (2)
- # onyx (26)
- # perun (14)
- # planck (5)
- # portland-or (34)
- # proton (2)
- # protorepl (8)
- # quil (1)
- # re-frame (6)
- # reagent (16)
- # remote-jobs (4)
- # ring (7)
- # ring-swagger (10)
- # rum (1)
- # untangled (2)
I am so glad retdinkdb got revived
@richiardiandrea Yeah, we make use of change feeds, and at times it feels like a minor superpower. And there's no other similar solutions in that space out there. So we're delighted too.
With the change in licencing, it suddenly looks like a viable solution again, although obviously community is everything now, and we'll be watching that closely.
@mikethompson @danielcompton re https://github.com/Day8/re-frame/issues/255 re “need to trigger an event dispatch whenever a given subscription value changes” there would be no requirement to attempt preventing people from shooting themselves in the foot so to speak right ? For example its easy enough to create an endless loop of modify db -> trigger event dispatch on subscription value change -> modify db -> .... ?