• Like
  • Save
Why HAML sucks or Why you should think before choosing HAML for your next project
Upcoming SlideShare
Loading in...5
×
 

Why HAML sucks or Why you should think before choosing HAML for your next project

on

  • 31,447 views

Audio required to make sense

Audio required to make sense

Statistics

Views

Total Views
31,447
Views on SlideShare
31,306
Embed Views
141

Actions

Likes
13
Downloads
46
Comments
14

6 Embeds 141

http://www.slideshare.net 128
https://twitter.com 4
https://si0.twimg.com 4
http://www.mefeedia.com 3
http://railslove.channelthing.com 1
http://cascadelandconservancy.wikispaces.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

110 of 14 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • I don't get it. What's the big deal about who sees your HAML. It compiles into HTML before it's interpreted by the browser. If the person who will be maintaining code doesn't get or bother to learn HAML, would they not just author the HTML from that point? I feel like it's a great tool for developers to shave some to large chunks of time off writing repetitive markup. Also, 'learn more about web standards'? What I like about HAML is it doesn't try and fix things for you like nonexistent tag names, attributes, etc. You're allowed to make mistakes and you can insert HTML if you don't like the way HAML does something or are unsure about what syntax for something is. I always like a fresh perspective, but the arguments here just weren't strong enough for me.
    Are you sure you want to
    Your message goes here
    Processing…
  • The only argument that people seem to have going for them as far as NOT using HAML is that it scares off front-end developers. But the truth is they never have to go anywhere near Ruby, get them to write all the JavaScript and HTML their little hearts desire and then run it through http://html2haml.heroku.com/ - DONE. (assuming of course a Ruby developer has to maintain the markup in the long-run).
    Are you sure you want to
    Your message goes here
    Processing…
  • Avoid using a wonderful templating engine because some developers are too lazy or afraid to learn it? No thanks.
    Are you sure you want to
    Your message goes here
    Processing…
  • I think it's your presentation that sucks, no offense. Work more on your argumentation.
    Are you sure you want to
    Your message goes here
    Processing…
  • I agree with this presenter - haml is yet another thing to learn, another layer, and who knows what support/interest it will have in 6 months or a year or 5 years. Write HTML - it's not going anywhere.
    Are you sure you want to
    Your message goes here
    Processing…

110 of 14

Post Comment
Edit your comment

    Why HAML sucks or Why you should think before choosing HAML for your next project Why HAML sucks or Why you should think before choosing HAML for your next project Presentation Transcript

    • Why HAML sucks
    • or
    • Why you should think before using HAML for your next project
    • Why people like HAML
    • A shorter, elegant way to write markup
    • You get to use sexy Ruby rather than smelly HTML
    • It feels goooood
    • It’s basically masturbation
    • That means playing alone
    • The bad
    • You need to understand indenting subtleties
    • (not very rubyish)
    • Front end developers have something in between them and their craft
    • Lets face it
    • Most developers write shitty HTML
    • Take Rails for inspiration if you don’t believe me
    • Inline javascript
    • Meaningless markup
    • Incorrect element usage
    • Poor accessibility
    • All are common traits of HTML, not HAML
    • HAML adds a layer to HTML that I don’t think is necessary
    • It's not fucking ruby either, dudes.
    • Comparison
    • I can’t be bothered getting a .net example
    • I get it
    • Its succinct
    • Its easy to read (it just takes a second at first)
    • but
    • Oh yeah? You do web stuff? My nephew made my website. He’s just like you - The real world
    • Myspace has terrible HTML (but people work it out)
    • & ass loads of blogging software
    • So, I guess in summary:
    • If you’re good at HTML and want to write less
    • If you and your coworkers are the only people who will ever look at your markup
    • If you’re cool with training up the new guy
    • Try HAML
    • Otherwise: Use and learn more about web standards
    • Don’t publish projects or code with higher boundaries than need be
    • Thanks