This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-22
Channels
- # admin-announcements (7)
- # beginners (56)
- # boot (69)
- # cider (168)
- # cljs-dev (2)
- # clojure (170)
- # clojure-austin (25)
- # clojure-beijing (3)
- # clojure-belgium (2)
- # clojure-france (3)
- # clojure-poland (17)
- # clojure-russia (115)
- # clojure-uk (40)
- # clojurebridge (3)
- # clojurescript (87)
- # cursive (9)
- # datomic (30)
- # dirac (18)
- # editors (3)
- # emacs (14)
- # hoplon (195)
- # immutant (14)
- # jobs (3)
- # jobs-discuss (4)
- # leiningen (11)
- # melbourne (5)
- # mount (42)
- # off-topic (5)
- # om (24)
- # onyx (48)
- # parinfer (53)
- # proton (1)
- # protorepl (2)
- # re-frame (3)
- # reactive (2)
- # reagent (29)
- # rum (5)
- # spacemacs (4)
- # untangled (91)
- # yada (1)
Alright I am going to bounce a concept off you guys for a little validation so I can either move on or remove this brain virus. I started wanting to make a react application and I love the flowing data of re-frame … but I very much dislike atoms (I know they are needed but something about them makes me feel icky technical term)
So I have this idea in my head to do kind of the same thing as re-frame but by tying an FRP library like Reagi to Rum.
So there will be the root application atom and components can “subscribe” to things just like in re-frame except those subscriptions are handled by a Reagi events signal and all of that is abstracted away under a Rum mixin so the components never get the actual atoms, just the results from the event signal as it changes.