This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-07
Channels
- # beginners (73)
- # boot (20)
- # chestnut (8)
- # cider (36)
- # clara (37)
- # cljs-dev (21)
- # cljs-experience (1)
- # cljsrn (2)
- # clojure (163)
- # clojure-austin (3)
- # clojure-dusseldorf (6)
- # clojure-finland (1)
- # clojure-ireland (4)
- # clojure-italy (45)
- # clojure-russia (9)
- # clojure-spec (47)
- # clojure-uk (20)
- # clojurescript (107)
- # cursive (24)
- # data-science (4)
- # datomic (4)
- # defnpodcast (1)
- # fulcro (1)
- # heroku (3)
- # jobs-discuss (4)
- # juxt (52)
- # lein-figwheel (1)
- # leiningen (4)
- # lumo (37)
- # midje (5)
- # off-topic (16)
- # onyx (15)
- # portkey (11)
- # re-frame (112)
- # reagent (12)
- # rum (1)
- # specter (35)
- # uncomplicate (6)
Hello there, a question related to ratom
s
Do they use react state internally
@juhoteperi thanks. Maybe you can help with https://clojurians.slack.com/archives/C0620C0C8/p1504600530000417
1. I’m preparing a talk about the advantages of reagent over react.js and I’d like to bring a concrete example
2. where and why caching is needed?
1. Is about comparing immutable structures, same benefits as with Immutable.js
2. Not sure what caching means here
1. How can we come up with a concrete benchmark/example that demonstrates the perfomance gain?
@viebel, about ratoms - React knows three ways to cause a component to be rerendered
1. changed this.props
2. manually re-running ReactDOM.render (which actually forces an update)
3. changed this.state
Reagent uses 2 to implement ratoms, not 3. Typical Reagent apps don't have any this.state. Even if you're using r/state
, that is actually implemented using a ratom IIRC