Marnen Laibow-Koser wrote: > Jeff Pritchard wrote: > [...] >> Thanks Steve, this is useful and interesting info. > > If you'd like another data point, I completely agree with Steve. Haml is > wonderful, and Sass is to ny knowledge the *only* tool that makes it > feasible to make CSS truly semantic and free of presentation classes. I > can't imagine doing without them again. > >> >> Just to clarify, my "side to side" analogy was intended to convey that >> some new tools did nothing to improve the Rails toolset -- some new >> tools moved app development sideways rather than forward. There have >> been plenty of "best thing since sliced bread" new ways to do things >> with Rails that have turned out to be just a distraction and which, in >> my view, were not an improvement over the "old way", and which have >> since faded away (apparently others agreed). > > There's always some of that in any evolving technology. > >> Sadly, some of those >> "bright ideas" were adopted by the Rails team, so we're stuck with those >> (like REST). > > REST is a big step forward, so this is probably an inapt example... > >> >> Thanks for the info on HAML and Compass >> jp > > Best, > -- > Marnen Laibow-Koser > http://www.marnen.org > [email protected]
Thanks Marnen. I've been studying HAML and SASS and Compass over the weekend, and I think I'm convinced. I'm going to do my next project with them and see how it goes. >> Sadly, some of those >> "bright ideas" were adopted by the Rails team, so we're stuck with those >> (like REST). > > REST is a big step forward, so this is probably an inapt example... THE EMPEROR HAS NO CLOTHES! :) (I know there are plenty of otherwise intelligent people who like it, but in my opinion, REST is dumb if you're not writing a web service - I see no advantage at all for a normal web application - and my feeble old brain refuses to be able to remember the darn path names - much easier to just use a hash of controller/action - and none of my clients is ever willing to allow a UI organization that is just straight-forward CRUD, always need custom actions, and the 'standard' crud just winds up as dead code ) -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
