This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-07
Channels
- # admin-announcements (1)
- # arachne (1)
- # beginners (11)
- # boot (72)
- # cider (7)
- # cljs-dev (9)
- # clojure (31)
- # clojure-czech (8)
- # clojure-poland (1)
- # clojure-russia (7)
- # clojure-uk (17)
- # clojurescript (48)
- # community-development (5)
- # cursive (2)
- # data-science (1)
- # datascript (3)
- # datavis (1)
- # datomic (4)
- # devcards (45)
- # docker (3)
- # hoplon (5)
- # keechma (3)
- # lein-figwheel (1)
- # leiningen (4)
- # luminus (16)
- # off-topic (1)
- # om (2)
- # om-next (1)
- # onyx (4)
- # other-languages (104)
- # overtone (1)
- # re-frame (2)
- # reagent (37)
- # rum (35)
- # untangled (4)
- # yada (4)
@niwinz: I read your blog post, very interesting. https://www.niwi.nz/2016/04/03/application-architecture-and-state-management-with-react-based-applications/
Oh @niwinz one question that I got when reading your post: can you change your app state through figwheel, or is it.. "hidden" inside the stream objects?
as I have explained, a function is already implement the pure state transofrmation protocol
and you have some atom that holds the whole app state somewhere, right? So you can just deref it?
so if you modify that atom with swap! or reset! that changes will be overwitten at some time (strictly speaking on the provided example and how I use that)
looks like a pretty good approach. Similar ideas as re-frame, and many others..? Though I do like the use of records
Hmm, yeah. Pretty much the same with me. I'm sure re-frame works great, but I'm a bit skeptical how it would scale when your app gets really big.. I'm in a project that's been going on for 1.5 years with 6 devs, and what I understand from re-frame, I worry that it wouldn't work for us
and I don't like use "frameworks" or libraries in the core of my application. I prefer use libraries on the corners and leve the application core under complete my domain