News for hackers. Stuff that matters.
Re:Haml Sucks for Content by jerhinesmith on Monday February 08, 2010 @01:48PM (#1110354)
Haml does allow for finer-grained control over whitespace, but even if that's not enough, when needed you can still "embed" plain-old html directly inside of your Haml files.

I guess I fail to see how html has any advantage over haml. The absolute worst case is that you're still writing html in 90+% of the cases (which you'd be doing anyway without haml), and in the best case, your markup becomes much more DRY and readable.

Re:Haml Sucks for Content by ehsanul on Monday February 08, 2010 @03:49PM (#1110654)
Well, I seem to always have formatting issues with haml, though probably because I haven't worked enough with haml yet to internalize the whitespace rules. No such issues with html of course. Not a huge advantage, but can make it annoying when you're first starting with haml.
Re:Haml Sucks for Content by jfarmer on Monday February 08, 2010 @02:26PM (#1110439)
HTML has an advantage because that's what people know, particularly designers.

Some designers I've worked with are ok with haml, others steadfastly refuse because their workflow is so HTML-centric.

Re:Haml Sucks for Content by chriseppstein on Monday February 08, 2010 @02:49PM (#1110482)
Tool support is a good reason to not use haml. I expect tool support will be there some day, but it's not really there yet. RubyMine has very nice haml support tho.