This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-29
Channels
- # architecture (14)
- # beginners (184)
- # boot (25)
- # cider (23)
- # clara (9)
- # cljsjs (13)
- # cljsrn (5)
- # clojure (140)
- # clojure-austria (1)
- # clojure-dev (24)
- # clojure-greece (15)
- # clojure-italy (7)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-sanfrancisco (10)
- # clojure-spec (39)
- # clojure-uk (28)
- # clojured (1)
- # clojurescript (26)
- # core-async (3)
- # cursive (13)
- # datomic (44)
- # docs (3)
- # emacs (31)
- # events (2)
- # figwheel (4)
- # fulcro (6)
- # graphql (2)
- # hoplon (5)
- # jobs (11)
- # juxt (4)
- # keechma (19)
- # leiningen (1)
- # off-topic (8)
- # om (8)
- # onyx (18)
- # parinfer (2)
- # re-frame (18)
- # reagent (24)
- # ring (4)
- # rum (2)
- # shadow-cljs (26)
- # sql (15)
- # timbre (6)
- # vim (2)
@thedavidmeister what I do now is pass on the original key to yet another multi-method which handles all :myattr/*
requests, the mutation observers in hoplon/brew are an example of this
mmm it's all a bit indirect though, you can do it of course but it would be nice if core was more directly extensible
which is kind of the point of your branch
@thedavidmeister I thought I would share another angle for describing dataflow that just popped into my head, this time not how it works but in how it transforms the developer experience. It occurred to me that expressing an app as so many independently conceived cell formulas does the same excellent job of decomposing a complex app as does the finite state machine approach to a problem, in which we are always focused on just one state and one input. Those are trivial to produce and yet a complex state handler emerges, one that is easy to debug and extend. Jes thinkin out loud.
@hiskennyness I totally agree!