<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>React on Brave New Geek</title><link>https://bravenewgeek.com/tag/react/</link><description>Recent content in React on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 May 2014 18:30:13 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/react/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Make with React and RequireJS</title><link>https://bravenewgeek.com/using-make-with-react-and-requirejs/</link><pubDate>Tue, 27 May 2014 18:30:13 -0600</pubDate><guid>https://bravenewgeek.com/using-make-with-react-and-requirejs/</guid><description>&lt;p&gt;&lt;a href="http://requirejs.org/"&gt;RequireJS&lt;/a&gt; is a great library for building modular JavaScript clients that conform to the &lt;a href="https://github.com/amdjs/amdjs-api/wiki/AMD"&gt;AMD API specification&lt;/a&gt;. It gives your JS an import-like mechanism by which you avoid global-namespace issues and makes your code behave more like a server-side language such as Python or Java. It also includes an optimization tool that can concatenate your JavaScript into a single file and minify it, which helps reduce HTTP overhead.&lt;/p&gt;
&lt;p&gt;I recently wrote about &lt;a href="http://www.bravenewgeek.com/building-user-interfaces-with-react/" title="Building User Interfaces with React"&gt;React&lt;/a&gt;, which is a library targeted at constructing UIs. React uses a special syntax called JSX for specifying DOM components in XML, and it compiles down to vanilla JavaScript. JSX can either be precompiled or compiled in the browser at runtime. The latter option has obvious performance implications and probably shouldn’t be used in production, but it works great for quickly hacking something together.&lt;/p&gt;</description></item><item><title>Building User Interfaces with React</title><link>https://bravenewgeek.com/building-user-interfaces-with-react/</link><pubDate>Wed, 21 May 2014 18:19:41 -0600</pubDate><guid>https://bravenewgeek.com/building-user-interfaces-with-react/</guid><description>&lt;p&gt;If you follow me on Twitter, you’ve probably heard me raving about &lt;a href="http://facebook.github.io/react/"&gt;React&lt;/a&gt;. React is described as a “JavaScript library for building user interfaces” and was open sourced by Facebook about a year ago. Everybody and their mom has a JavaScript framework, so what makes React so interesting? Why would you use it over mainstays like Backbone or Angular?&lt;/p&gt;
&lt;p&gt;There are a few things that make React worth looking at. First, React is a &lt;em&gt;library&lt;/em&gt;, not a framework. It makes no assumptions about your frontend stack, and it plays nicely with existing codebases, regardless of the tech you’re using. This is great because you can use React incrementally for new or legacy code. Write your whole UI with it or use it for a single feature. All you need is a DOM node to mount.&lt;/p&gt;</description></item></channel></rss>