Preprocessors like CoffeeScript are pretty silly because they require
the programmer to learn two languages rather than one (If the
programmer actually cares to ensure acceptable JavaScript is being
generated). If a professional is expected to know JavaScript why take
them out of that familiar context?

HAML, like CoffeeScript, is more readable than the typical alternative
but it requires every front-end and back-end developer to learn a new
syntax. It makes more sense to either take the designer-friendly route
with Erubis or the developer-friendly route with Erector. I would
select the latter in most cases.



On Jun 8, 1:57 pm, Adam Grant <[email protected]> wrote:
> Hi guys,
>
> Preface: I've never used Haml.  Here are some of my reasons for not using
> it, aside from not *needing* to:
>
> For a templating system for HTML, I would have a hard time moving to a
> totally abstracted syntax like Haml. I think Erb-like templaters only
> intercede where absolutely necessary to build the HTML elements. If you can
> read HTML, you can understand most .erb files, maybe minus the few Rails
> (insert-fav-framework-here) view helpers.  If you need to move away from
> Haml at some point down the line, I could imagine it being a real pain to
> migrate all your views (I'm sure there are migration libraries though). I
> like keeping the HTML mostly intact so that it is easier for others to
> support the project if the Haml guru's leave.
>
> The same goes for something like CoffeeScript. If you are coding in
> Javascript, just write it. It's not THAT bad. Libraries like jQuery help
> easy the keyboard strain. Having a completely abstracted syntax for
> something else that gets translated and rendered into a different language
> can cause legacy maintenance issues down the road. Popular libraries change
> fast, but things like HTML and JS don't as much. Library support gets
> dropped for a lot of little projects in the Open Source world over time.
>
> That being said, I would welcome the chance to use CoffeeScript or Haml at
> some point. My mind is open to them, but I'm wary.
>
> - Adam
>

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to