On 28 Sep 2008, at 14:56, RSL wrote: > Awesome good news for those few projects where bullheaded devs won't > let us use Haml but don't care what we do with the CSS.
There are good reasons for doing this, by the way. Haml is great but obviously it never will (and never intends to) displace HTML as the native language of front-end web developers, so migrating a project to Haml carries a small maintenance risk of making all markup inaccessible to real or imaginary future template developers. (Haml couldn't be simpler, but this list adequately demonstrates that even the simplest possible markup with the clearest possible error messages will still be confusing to some people.) And once you've converted everything to Haml, there's no automated way back AFAIK, so it's a nontrivial commitment. Sass, however, is a risk-free no-brainer: use it now to make stylesheet maintenance easier, but since it's just generating static CSS you'll always have the option of effortlessly dropping it later if anyone has a problem with it. Which is why I kind of wish there was a proper standalone Sass distribution (i.e. Haml & Sass without the Haml, not a Shoes app). Cheers, -Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
