<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for Open eyes Working brain</title>
	<atom:link href="http://federico.galassi.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://federico.galassi.net</link>
	<description>dedicated, in respect and admiration, to the spirit that lives in the computer</description>
	<lastBuildDate>Mon, 26 Sep 2011 18:27:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>Comment on Die Semicolon Die! by federico</title>
		<link>http://federico.galassi.net/2011/05/25/die-semicolon-die/comment-page-1/#comment-8017</link>
		<dc:creator>federico</dc:creator>
		<pubDate>Mon, 26 Sep 2011 18:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=362#comment-8017</guid>
		<description>I&#039;d say yes, python space treatment seems to improve code clarity</description>
		<content:encoded><![CDATA[<p>I&#8217;d say yes, python space treatment seems to improve code clarity</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Die Semicolon Die! by Giuseppe</title>
		<link>http://federico.galassi.net/2011/05/25/die-semicolon-die/comment-page-1/#comment-8007</link>
		<dc:creator>Giuseppe</dc:creator>
		<pubDate>Mon, 26 Sep 2011 10:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=362#comment-8007</guid>
		<description>Isn&#039;t Python syntax more elegant in its &quot;space matters&quot; simplicity, is it?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t Python syntax more elegant in its &#8220;space matters&#8221; simplicity, is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Die Semicolon Die! by Stefano Bagnara</title>
		<link>http://federico.galassi.net/2011/05/25/die-semicolon-die/comment-page-1/#comment-5472</link>
		<dc:creator>Stefano Bagnara</dc:creator>
		<pubDate>Wed, 25 May 2011 18:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=362#comment-5472</guid>
		<description>&quot;Avoid starting a line with ( [ +  - / but if you have to, prepend it with a semicolon&quot;
And you call this &quot;elengant&quot; ?? ;-)

We definitely have different elegance definitions!

I agree that ASI is one of the bad parts of javascript. My elegant solution is to remove ASI and forcing semicolon at the end of each statement.

In italian (and maybe most western languages) we use the &quot;full stop&quot; (dot) to complete a sentence, but most time you can tell anyway where the end is because you don&#039;t have more words in the same line and the following line starts with an uppercase.

So: would Italian be more elegant by removing full stops at the end of the last sentence of each paragraph? I will loudly say &quot;NO please&quot; if you ask me. :-)</description>
		<content:encoded><![CDATA[<p>&#8220;Avoid starting a line with ( [ +  &#8211; / but if you have to, prepend it with a semicolon&#8221;<br />
And you call this &#8220;elengant&#8221; ?? ;-)</p>
<p>We definitely have different elegance definitions!</p>
<p>I agree that ASI is one of the bad parts of javascript. My elegant solution is to remove ASI and forcing semicolon at the end of each statement.</p>
<p>In italian (and maybe most western languages) we use the &#8220;full stop&#8221; (dot) to complete a sentence, but most time you can tell anyway where the end is because you don&#8217;t have more words in the same line and the following line starts with an uppercase.</p>
<p>So: would Italian be more elegant by removing full stops at the end of the last sentence of each paragraph? I will loudly say &#8220;NO please&#8221; if you ask me. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Wave Fallacy by Complexity killed the Wave &#124; Open eyes Working brain</title>
		<link>http://federico.galassi.net/2009/06/09/google-wave-fallacy/comment-page-1/#comment-1395</link>
		<dc:creator>Complexity killed the Wave &#124; Open eyes Working brain</dc:creator>
		<pubDate>Fri, 06 Aug 2010 22:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=67#comment-1395</guid>
		<description>[...] That&#8217;s a great example of why &#8220;do one thing well&#8221; is better than &#8220;do it all&#8221;. Not only because, as Gall&#8217;s law implies, it&#8217;s easier to get a simple system straight, but also because once you get a complex system straight, you still have to make people get their mind around it. Wave made chat and e-mail play well together, with a great replay feature, bots and translation. Twitter gives short text updates. Adoption declared the winner, but we already knew it. [...]</description>
		<content:encoded><![CDATA[<p>[...] That&#8217;s a great example of why &#8220;do one thing well&#8221; is better than &#8220;do it all&#8221;. Not only because, as Gall&#8217;s law implies, it&#8217;s easier to get a simple system straight, but also because once you get a complex system straight, you still have to make people get their mind around it. Wave made chat and e-mail play well together, with a great replay feature, bots and translation. Twitter gives short text updates. Adoption declared the winner, but we already knew it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Javascript Performance: Make the Browser Happy (and You Sad) by Jacopo Romei</title>
		<link>http://federico.galassi.net/2009/11/15/javascript-performance-make-the-browser-happy-and-you-sad/comment-page-1/#comment-1268</link>
		<dc:creator>Jacopo Romei</dc:creator>
		<pubDate>Sun, 11 Jul 2010 01:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=193#comment-1268</guid>
		<description>So wise of you: &quot;don’t turn yourself into a machine, you’d be an awful one&quot;.
Thanks for this post.</description>
		<content:encoded><![CDATA[<p>So wise of you: &#8220;don’t turn yourself into a machine, you’d be an awful one&#8221;.<br />
Thanks for this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Javascript Performance: Make the Browser Happy (and You Sad) by Please Don&#8217;t Touch the Slow Parts &#124; Open eyes Working brain</title>
		<link>http://federico.galassi.net/2009/11/15/javascript-performance-make-the-browser-happy-and-you-sad/comment-page-1/#comment-1095</link>
		<dc:creator>Please Don&#8217;t Touch the Slow Parts &#124; Open eyes Working brain</dc:creator>
		<pubDate>Sat, 08 May 2010 09:58:14 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=193#comment-1095</guid>
		<description>[...] not as flat list but under macro-areas emerged as &#8220;slow parts&#8221;. Also, i concluded with my obsession that complexity inherently introduced by performance optimizations should not be dealt with by [...]</description>
		<content:encoded><![CDATA[<p>[...] not as flat list but under macro-areas emerged as &#8220;slow parts&#8221;. Also, i concluded with my obsession that complexity inherently introduced by performance optimizations should not be dealt with by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Happy Birthday Blog by Massimiliano Arione</title>
		<link>http://federico.galassi.net/2010/04/03/happy-birthday-blog/comment-page-1/#comment-1045</link>
		<dc:creator>Massimiliano Arione</dc:creator>
		<pubDate>Sat, 03 Apr 2010 13:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=308#comment-1045</guid>
		<description>Cheers! :-)</description>
		<content:encoded><![CDATA[<p>Cheers! :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hello World by Happy Birthday Blog &#124; Open eyes Working brain</title>
		<link>http://federico.galassi.net/2009/04/03/hello-world/comment-page-1/#comment-1044</link>
		<dc:creator>Happy Birthday Blog &#124; Open eyes Working brain</dc:creator>
		<pubDate>Sat, 03 Apr 2010 13:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=9#comment-1044</guid>
		<description>[...] one year ago i posted for the first time here. An hello world tentatively saying &#8220;Let&#8217;s see what happens&#8221;. Now, a year, 16 posts and more than [...]</description>
		<content:encoded><![CDATA[<p>[...] one year ago i posted for the first time here. An hello world tentatively saying &#8220;Let&#8217;s see what happens&#8221;. Now, a year, 16 posts and more than [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Web Authentication as it SHOULD have been by Jacopo Romei</title>
		<link>http://federico.galassi.net/2009/12/31/web-authentication-as-it-should-have-been/comment-page-1/#comment-1005</link>
		<dc:creator>Jacopo Romei</dc:creator>
		<pubDate>Fri, 08 Jan 2010 15:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=214#comment-1005</guid>
		<description>Pensare ai bivi (facili) che la Storia ha gestito male solleva in me un misto di ansia e noia...</description>
		<content:encoded><![CDATA[<p>Pensare ai bivi (facili) che la Storia ha gestito male solleva in me un misto di ansia e noia&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Refactoring to Unobtrusive Javascript by Talks: Refactoring to Unobtrusive Javascript &#124; JavascriptCamp</title>
		<link>http://federico.galassi.net/2009/09/28/refactoring-to-unobtrusive-javascript/comment-page-1/#comment-687</link>
		<dc:creator>Talks: Refactoring to Unobtrusive Javascript &#124; JavascriptCamp</dc:creator>
		<pubDate>Fri, 02 Oct 2009 06:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://federico.galassi.net/?p=159#comment-687</guid>
		<description>[...] Federico Galassi ha introdotto alcune buone pratiche per rifattorizzare applicazioni Javascript usando criteri di separation of concerns al fine di dividere bussiness logic, visualizzazione e contenuti. [...]</description>
		<content:encoded><![CDATA[<p>[...] Federico Galassi ha introdotto alcune buone pratiche per rifattorizzare applicazioni Javascript usando criteri di separation of concerns al fine di dividere bussiness logic, visualizzazione e contenuti. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

