{"patch":"diff --git a\/docs\/_posts\/2013-11-06-community-roundup-10.md b\/docs\/_posts\/2013-11-06-community-roundup-10.md\nnew file mode 100644\nindex 0000000000..fa83a4745c\n--- \/dev\/null\n+++ b\/docs\/_posts\/2013-11-06-community-roundup-10.md\n@@ -0,0 +1,125 @@\n+---\n+title: \"Community Round-up #10\"\n+layout: post\n+author: Vjeux\n+---\n+\n+This is the 10th round-up already and React has come quite far since it was open sourced. Almost all new web projects at Khan Academy, Facebook, and Instagram are being developed using React. React has been deployed in a variety of contexts: a Chrome extension, a Windows 8 application, mobile websites, and desktop websites supporting Internet Explorer 8! Language-wise, React is not only being used within JavaScript but also CoffeeScript and ClojureScript.\n+\n+The best part is that no drastic changes have been required to support all those use cases. Most of the efforts were targeted at polishing edge cases, performance improvements, and documentation.\n+\n+## Khan Academy - Officially moving to React\n+\n+[Joel Burget](http:\/\/joelburget.com\/) announced at Hack Reactor that new front-end code at Khan Academy should be written in React!\n+\n+> How did we get the rest of the team to adopt React? Using interns as an attack vector! Most full-time devs had already been working on their existing projects for a while and weren't looking to try something new at the time, but our class of summer interns was just arriving. For whatever reason, a lot of them decided to try React for their projects. Then mentors became exposed through code reviews or otherwise touching the new code. In this way React knowledge diffused to almost the whole team over the summer.\n+>\n+> Since the first React checkin on June 5, we've somehow managed to accumulate 23500 lines of jsx (React-flavored js) code. Which is terrifying in a way - that's a lot of code - but also really exciting that it was picked up so quickly.\n+>\n+> We held three meetings about how we should proceed with React. At the first two we decided to continue experimenting with React and deferred a final decision on whether to adopt it. At the third we adopted the policy that new code should be written in React.\n+>\n+> I'm excited that we were able to start nudging code quality forward. However, we still have a lot of work to do! One of the selling points of this transition is adopting a uniform frontend style. We're trying to upgrade all the code from (really old) pure jQuery and (regular old) Backbone views \/ Handlebars to shiny React. At the moment all we've done is introduce more fragmentation. We won't be gratuitously updating working code (if it ain't broke, don't fix it), but are seeking out parts of the codebase where we can shoot two birds with one stone by rewriting in React while fixing bugs or adding functionality.\n+>\n+> [Read the full article](http:\/\/joelburget.com\/backbone-to-react\/)\n+\n+\n+## React: Rethinking best practices\n+\n+[Pete Hunt](http:\/\/www.petehunt.net\/)'s talk at JSConf EU 2013 is now available in video.\n+\n+

dillon1000/react

Files changed