> Like Matt, I feel like HAML is nice, but comes at the cost of being harder > for non-devs to use. Patrick may be tired of hearing that as a reason, but > that certainly doesn't make it any less valid now than it was 5 years ago. > Sorry dude, I know you are an amazing designer / developer, but that is a > rare bird and the rest of us are frequently dealing with people who say > things like "Wait a minute, I have to go through all of this just to load the > app AND learn a new mark up language? Can't I just edit some HTML files on > and FTP server some where?" It is a serious concern.
So why should we even use Rails then? Isn't manually uploading files easier? Let's just use PHP! Your argument makes way more sense when you're talking about clients. Clients shouldn't need to learn HAML or, for that matter, even HTML. If they need to edit the app, they should be doing so through an admin dashboard, not mucking around with templates on their own. But, when it comes to front-end designers -- who, in general, should know how to hand code a complex HTML document -- learning HAML just isn't a big deal. You can pick up the basic syntax in 15 minutes, and the edge case stuff (setting custom attributes, escaping, etc.) maybe another 30 minutes. In a world where people already know HTML, Markdown, BBCode, etc., the only real barrier to learning HAML is laziness. -- Patrick -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
