<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>pragmatic void</title>
	<atom:link href="http://adibaron.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://adibaron.com/blog</link>
	<description></description>
	<lastBuildDate>Tue, 23 Apr 2013 16:45:11 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Pointless.js (Better) Explained</title>
		<link>http://adibaron.com/blog/2013/03/pointless-js-better-explained/</link>
		<comments>http://adibaron.com/blog/2013/03/pointless-js-better-explained/#comments</comments>
		<pubDate>Sun, 24 Mar 2013 19:50:10 +0000</pubDate>
		<dc:creator>adi</dc:creator>
				<category><![CDATA[Backbone.js]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://adibaron.com/blog/?p=1067</guid>
		<description><![CDATA[In my previous post about Backbone I chose not to go into details. Apparently, even though appreciated, the bottom line wasn’t enough. People expect explanations&#8230; So I decided to write another post that better explains why I think Backbone should be avoided as infrastructure for web applications (not web sites). However, since I didn’t want ...<a class="post-readmore" href="http://adibaron.com/blog/2013/03/pointless-js-better-explained/">read more</a>]]></description>
		<wfw:commentRss>http://adibaron.com/blog/2013/03/pointless-js-better-explained/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pointless.js</title>
		<link>http://adibaron.com/blog/2013/03/pointless-js/</link>
		<comments>http://adibaron.com/blog/2013/03/pointless-js/#comments</comments>
		<pubDate>Sat, 23 Mar 2013 13:16:40 +0000</pubDate>
		<dc:creator>adi</dc:creator>
				<category><![CDATA[Backbone.js]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://adibaron.com/blog/?p=1035</guid>
		<description><![CDATA[Backbone.js is a pointless piece of code! If you need a framework for your web application, do yourself a favor and stay away. You&#8217;re probably wondering about how this can be true, right? I mean, after all, there must be a reason behind Backbone’s success&#8230; Well, of course there’s a reason. It is one that ...<a class="post-readmore" href="http://adibaron.com/blog/2013/03/pointless-js/">read more</a>]]></description>
		<wfw:commentRss>http://adibaron.com/blog/2013/03/pointless-js/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node Modules</title>
		<link>http://adibaron.com/blog/2013/01/node-modules/</link>
		<comments>http://adibaron.com/blog/2013/01/node-modules/#comments</comments>
		<pubDate>Wed, 02 Jan 2013 19:00:55 +0000</pubDate>
		<dc:creator>adi</dc:creator>
				<category><![CDATA[Node.js]]></category>
		<category><![CDATA[exports]]></category>
		<category><![CDATA[module]]></category>
		<category><![CDATA[node_modules]]></category>
		<category><![CDATA[require]]></category>

		<guid isPermaLink="false">http://adibaron.com/blog/?p=178</guid>
		<description><![CDATA[Building complex applications with JavaScript isn&#8217;t a straightforward task because the language has no standard mechanism for creating libraries. CommonJS module specification suggests a way in which libraries (modules) should be written &#8220;in order to be interoperable among a class of module systems that can be both client and server side&#8221;. Node implements a similar system that makes ...<a class="post-readmore" href="http://adibaron.com/blog/2013/01/node-modules/">read more</a>]]></description>
		<wfw:commentRss>http://adibaron.com/blog/2013/01/node-modules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node exports &amp; require</title>
		<link>http://adibaron.com/blog/2012/12/node-exports-require/</link>
		<comments>http://adibaron.com/blog/2012/12/node-exports-require/#comments</comments>
		<pubDate>Sat, 29 Dec 2012 18:48:29 +0000</pubDate>
		<dc:creator>adi</dc:creator>
				<category><![CDATA[Node.js]]></category>
		<category><![CDATA[exports]]></category>
		<category><![CDATA[module]]></category>
		<category><![CDATA[node_modules]]></category>
		<category><![CDATA[require]]></category>

		<guid isPermaLink="false">http://adibaron.com/blog/?p=567</guid>
		<description><![CDATA[In my post about Node modules I demonstrate the usage of require() and exports without going into detail. Structuring a Node deployment can be tricky, mostly because there&#8217;s more than one way to organize modules in the file system (particularly when working with npm, the de-facto package management tool for Node). Knowing how require() and exports work is important, ...<a class="post-readmore" href="http://adibaron.com/blog/2012/12/node-exports-require/">read more</a>]]></description>
		<wfw:commentRss>http://adibaron.com/blog/2012/12/node-exports-require/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
