This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-28
Channels
- # admin-announcements (1)
- # aws (2)
- # beginners (21)
- # boot (28)
- # braid-chat (1)
- # cider (51)
- # cljs-edn (7)
- # cljsjs (35)
- # cljsrn (2)
- # clojure (85)
- # clojure-chicago (7)
- # clojure-czech (1)
- # clojure-gamedev (3)
- # clojure-poland (2)
- # clojure-russia (80)
- # clojure-sanfrancisco (1)
- # clojure-uk (5)
- # clojurebridge (9)
- # clojurescript (68)
- # cursive (29)
- # datomic (23)
- # emacs (2)
- # hoplon (94)
- # jobs-discuss (15)
- # juxt (2)
- # liberator (2)
- # luminus (16)
- # mount (12)
- # off-topic (7)
- # om (57)
- # onyx (58)
- # proton (10)
- # re-frame (9)
- # reagent (38)
- # remote-jobs (2)
- # rum (12)
- # untangled (136)
@malcolmsparks: There are large parallels between a component-ized (as in the start/stop protocols) complex server app and an Om.Next/React style UI. (Non UI)Components don’t promote reusability unless there’s something like what Om.Next presents. I realize now that is sort of what I was trying to do with Aero, albeit poorly. (Translate between graph/tree). I do think your simplifications are ultimately going to pay off in the long run.
I’ll keep this kicking around the back of my brain, I think there might be some wins here (not necessarily with aero) regarding systems that heavily embrace component.