{"commit":{"shortRevision":"88d0c81680","authoredAt":"2014-07-27T14:19:55+02:00","authorName":"Christopher Chedeau","subject":"Merge pull request #1942 from LoukaN\/roundup_20","authorEmail":"vjeuxx@gmail.com","revision":"88d0c816803590d51a369471e2a6ec0ec13d0403"},"files":[{"status":"A","path":"docs\/_posts\/2014-07-28-community-roundup-20.md"},{"status":"A","path":"docs\/img\/blog\/kendoui.png"}],"patch":"diff --git a\/docs\/_posts\/2014-07-28-community-roundup-20.md b\/docs\/_posts\/2014-07-28-community-roundup-20.md\nnew file mode 100644\nindex 0000000000..6611d4eaeb\n--- \/dev\/null\n+++ b\/docs\/_posts\/2014-07-28-community-roundup-20.md\n@@ -0,0 +1,116 @@\n+---\n+title: \"Community Round-up #20\"\n+layout: post\n+author: Lou Husson\n+---\n+\n+It's an exciting time for React as there are now more commits from open source contributors than Facebook engineers! Keep up the good work :)\n+\n+## Atom moves to React\n+\n+[Atom, GitHub's code editor, is now using React](http:\/\/blog.atom.io\/2014\/07\/02\/moving-atom-to-react.html) to build the editing experience. They did the move in order to improve performance. By default, React helped them eliminate unnecessary reflows. Then, they were able to architecture the rendering pipeline in order to minimize repaint with hardware acceleration. This is a testament that React's architecture is viable for high performant applications.\n+\n+[

](http:\/\/blog.atom.io\/2014\/07\/02\/moving-atom-to-react.html)\n+\n+\n+## Why Does React Scale?\n+\n+At the last [JSConf.us](http:\/\/2014.jsconf.us\/), Vjeux talked about the design decisions of the API that makes it scale for large number of developers. If you don't have 20 minutes, take a look at the [annotated slides](https:\/\/speakerdeck.com\/vjeux\/why-does-react-scale-jsconf-2014).\n+\n+

dillon1000/react

Files changed