Re:First Impressions Using React Native
by adrianm on Friday February 06, 2015 @12:10PM
(#9009995)
Om is fast at checking if a component's state has changed because you can do a very fast identity comparison on the persistent hash map holding state, but persistent data structures are not faster than their mutable cousins simply because of immutability. That immutability leads to significantly more objects being allocated, which means to really take advantage of these features in a managed language you need a VM with a very high performance garbage collector. This is partly why Clojure on the JVM works so well. That being said, non JIT compiled JavaScript VMs generally provide terrible performance for ClojureScript. I do not believe JavaScriptCore JITs anything, so I don't know how immediately useful ClojureScript with React Native will be outside of toy examples.
[ Parent
| on HN ]
> That immutability leads to significantly more objects being allocated
What about shared immutable data structures?
Re:First Impressions Using React Native
by tree_of_item on Saturday February 07, 2015 @01:05AM
(#9013245)
Clojure uses structural sharing of course, but that was taken in to account in the parent comment. It's still a lot of allocation.
Re:First Impressions Using React Native
by danabramov on Friday February 06, 2015 @12:40PM
(#9010261)
Fair points.