clarify why react is not good for vr

supermedium · May 17, 2018 · 020e975 · 020e975
1 parent 1bbb267
commit 020e975
Show file tree

Hide file tree

Showing 2 changed files with 14,003 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 <h1 align="center">aframe-react</h1>
 
-> I currently recommend using vanilla A-Frame and [aframe-state-component](https://npmjs.org/aframe-state-component) with [static templating](https://mozilla.github.io/nunjucks/) over `aframe-react`.
+> I recommend using vanilla A-Frame and [aframe-state-component](https://npmjs.org/aframe-state-component) with [static templating](https://mozilla.github.io/nunjucks/) over `aframe-react`. React wastes a lot of cycles and incurs a lot of memory garbage. aframe-react is often abused where it is too easy to place 3D/real-time logic at the React layer, causing poor performance (e.g., doing React renders on ticks). Internally, React does tons of computation to compute what changed, and flushes it to the entire application. It is apparent React ecosystem does not care much about memory as most examples allocate functions and objects in the render method, and where immutables are popular. With only ~10ms per frame to do all computation, there is little room for React's massive system.
 
 <br/>