<?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 on: Why I don&#8217;t like HAML</title>
	<atom:link href="http://blog.getify.com/why-i-dont-like-haml/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.getify.com/why-i-dont-like-haml/</link>
	<description>javascript, performance, and ui musings</description>
	<lastBuildDate>Mon, 07 May 2012 16:42:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Zequez</title>
		<link>http://blog.getify.com/why-i-dont-like-haml/comment-page-1/#comment-2322</link>
		<dc:creator>Zequez</dc:creator>
		<pubDate>Sun, 01 Apr 2012 23:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getify.com/?p=168#comment-2322</guid>
		<description>I also disagree entirely, and about the hash &quot;sandwich&quot;, since Ruby 1.9 you can just do the following:

%sandwich{bread: &#039;whole wheat&#039;, filling: &#039;peanut butter and jelly&#039;,
delicious: true}

And most text editors / IDEs highlight the indentation you are in, so there is no need to have a closing tag.

And HAML precompiles to ERB.</description>
		<content:encoded><![CDATA[<p>I also disagree entirely, and about the hash &#8220;sandwich&#8221;, since Ruby 1.9 you can just do the following:</p>
<p>%sandwich{bread: &#8216;whole wheat&#8217;, filling: &#8216;peanut butter and jelly&#8217;,<br />
delicious: true}</p>
<p>And most text editors / IDEs highlight the indentation you are in, so there is no need to have a closing tag.</p>
<p>And HAML precompiles to ERB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: getify</title>
		<link>http://blog.getify.com/why-i-dont-like-haml/comment-page-1/#comment-2006</link>
		<dc:creator>getify</dc:creator>
		<pubDate>Fri, 04 Mar 2011 01:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getify.com/?p=168#comment-2006</guid>
		<description>@Hugo- You&#039;re absolutely correct, I&#039;ve been lax in my writing of blog posts lately... and especially so in terms of describing how to use HandlebarJS. It *is* under active development, but I just haven&#039;t been writing about it much, and I should. I&#039;ll add that topic to my queue and try to get to that soon. Thanks for the feedback.</description>
		<content:encoded><![CDATA[<p>@Hugo- You&#8217;re absolutely correct, I&#8217;ve been lax in my writing of blog posts lately&#8230; and especially so in terms of describing how to use HandlebarJS. It *is* under active development, but I just haven&#8217;t been writing about it much, and I should. I&#8217;ll add that topic to my queue and try to get to that soon. Thanks for the feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugo Estrada</title>
		<link>http://blog.getify.com/why-i-dont-like-haml/comment-page-1/#comment-2005</link>
		<dc:creator>Hugo Estrada</dc:creator>
		<pubDate>Fri, 04 Mar 2011 00:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getify.com/?p=168#comment-2005</guid>
		<description>I don&#039;t know if I would agree with what you say, but I do agree in your philosophy that we should keep things as simple as possible. 

Your post begs the question on what is a better way to template. Seeing that you have been working on HandlebarJS for a while, why don&#039;t you also include other posts where you describe how to use it together with your technical justification? If you don&#039;t have that, I would love to read that future entry.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if I would agree with what you say, but I do agree in your philosophy that we should keep things as simple as possible. </p>
<p>Your post begs the question on what is a better way to template. Seeing that you have been working on HandlebarJS for a while, why don&#8217;t you also include other posts where you describe how to use it together with your technical justification? If you don&#8217;t have that, I would love to read that future entry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: getify</title>
		<link>http://blog.getify.com/why-i-dont-like-haml/comment-page-1/#comment-105</link>
		<dc:creator>getify</dc:creator>
		<pubDate>Wed, 12 May 2010 00:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getify.com/?p=168#comment-105</guid>
		<description>@John -- it didn&#039;t take very long reading the documentation for me to see the parts I don&#039;t like about HAML. Were HAML my only option and I was still stubbing my toes on all those &quot;ui architecture&quot; issues you refer to, I might be inclined to take a second look. 

But instead, I decided to not just complain but do something about it, so I wrote something that worked the way I &lt;strong&gt;do&lt;/strong&gt; like, which is what turned out to be the &lt;a href=&quot;http://github.com/getify/HandlebarJS&quot; rel=&quot;nofollow&quot;&gt;HandlebarJS&lt;/a&gt; templating engine. I can say pretty surely that writing HTML templates with JSON data and minimal templating logic is &lt;em&gt;the way&lt;/em&gt; I think templating should be, so I consider HAML to be an inferior option in most ways.

But I do appreciate your perspective and comments -- keep &#039;em coming!</description>
		<content:encoded><![CDATA[<p>@John &#8212; it didn&#8217;t take very long reading the documentation for me to see the parts I don&#8217;t like about HAML. Were HAML my only option and I was still stubbing my toes on all those &#8220;ui architecture&#8221; issues you refer to, I might be inclined to take a second look. </p>
<p>But instead, I decided to not just complain but do something about it, so I wrote something that worked the way I <strong>do</strong> like, which is what turned out to be the <a href="http://github.com/getify/HandlebarJS" rel="nofollow">HandlebarJS</a> templating engine. I can say pretty surely that writing HTML templates with JSON data and minimal templating logic is <em>the way</em> I think templating should be, so I consider HAML to be an inferior option in most ways.</p>
<p>But I do appreciate your perspective and comments &#8212; keep &#8216;em coming!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.getify.com/why-i-dont-like-haml/comment-page-1/#comment-104</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 11 May 2010 23:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getify.com/?p=168#comment-104</guid>
		<description>I just use Textmate, and the indent levels are pretty obvious to me from a quick glance.  If I&#039;m not sure which column the line starts on, I guess I can put the cursor on the first character and look at the column/row values. Either way, it&#039;s never been a problem or hassle for me.  

That&#039;s odd that HAML tells you to define a hash in the documentation, but maybe they are just trying to illustrate how this can be done, which I guess could be incredibly useful if, say, you have a long succession of HTML values that you need to repeatedly pass the same attributes to.

Anyway, documentation is never the strong suit of anything in the ruby/rails world.

How long did you try HAML before decided you didn&#039;t like it?  I am not trying to be a jerk, I&#039;m just curious because I did say all of these same things until I forced myself to try it again -- it was the extreme frustration of 
horribly ugly ERB code, cluttered up with  everywhere, and all those useless  tags -- that made me give it another shot.  And it only took me, I dunno, two hours or so -- before I became somewhat evangelical about it.  (And I&#039;m not really particularly evangelical about anything!)</description>
		<content:encoded><![CDATA[<p>I just use Textmate, and the indent levels are pretty obvious to me from a quick glance.  If I&#8217;m not sure which column the line starts on, I guess I can put the cursor on the first character and look at the column/row values. Either way, it&#8217;s never been a problem or hassle for me.  </p>
<p>That&#8217;s odd that HAML tells you to define a hash in the documentation, but maybe they are just trying to illustrate how this can be done, which I guess could be incredibly useful if, say, you have a long succession of HTML values that you need to repeatedly pass the same attributes to.</p>
<p>Anyway, documentation is never the strong suit of anything in the ruby/rails world.</p>
<p>How long did you try HAML before decided you didn&#8217;t like it?  I am not trying to be a jerk, I&#8217;m just curious because I did say all of these same things until I forced myself to try it again &#8212; it was the extreme frustration of<br />
horribly ugly ERB code, cluttered up with  everywhere, and all those useless  tags &#8212; that made me give it another shot.  And it only took me, I dunno, two hours or so &#8212; before I became somewhat evangelical about it.  (And I&#8217;m not really particularly evangelical about anything!)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Content Delivery Network via getiblog.2static.it

Served from: blog.getify.com @ 2012-05-18 07:54:01 -->
