I don't see how putting it in the Gemfile is a win. Anyone who wants coffeescript is perfectly capable of adding it themselves along with all the other gems they usually add to their projects. If they're like me they just have a Gemfile they drop into any new project (or if they're fancy then they're using their own app template). So, no one can convince me that the experienced developer is the use-case for this choice.
Any newbie will more than likely only know HTML, CSS and JS so will stick with editing ERB, CSS and JS files. They'll just carry a useless coffee-script along with their app. So, doesn't meet any need there either. So, I'm struggling to see the purpose of doing this at all. Is it as simple as giving coffeescript (and SASS) an official Rails stamp of approval? Do those of us who help total newbies in #ror and other forums a favor and please just leave it commented out. On Wed, Apr 13, 2011 at 11:34 AM, Steve Klabnik <[email protected]>wrote: > The history of Rails has always been one of choosing a default, and being > opinionated about it. While I'd prefer haml before coffeescript, I think > it's a perfectly reasonable choice for Rails to make. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" 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-core?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
