Software developers may not have to design their own HTML, but they sure as hell have to write it.
HTML is a huge pain in the ass to write:
* It requires balancing tags
* It's verbose
* It is crudded up with syntax (</-="") and keywords
* It consistently runs right off the 80 column right margin
* It's an enormous pain to extend
* It's slow to read; for instance, try picking the plural version of a constantly-used class name out of tag soup
Haml isn't a shortcut to writing HTML. On the contrary, to use it well, you have to know HTML well. What Haml does is to solve the problems that make HTML a pain to use to express user interface in.
Whereas
HAML
is
notInline your HTML: That’s right. Just put some HTML into your Haml document. Don’t be afraid, it’ll be just fine.
Filters aren't a "workaround," they are the part of the language for handling content.
http://haml-lang.com/docs/yardoc/file.HAML_REFERENCE.html#fi...
I don't like his title either, but he gets to write whatever he wants about Haml.
Update... That was Chris' explanation!