3 ms·
By default, really? I don't like the idea neither I'm a Rails developer, but I think that this will increase the learning curve. Let it be just a choice.
by caioariede 16y ago
By default, really?
I don't like the idea neither I'm a Rails developer, but I think that this will increase the learning curve.
Let it be just a choice.
- scottbessler 16y agoIt being a default is not mutually exclusive with it being a choice. I like the move, defaults should be used to push forward positive change and very few if anyone seems to have said they would rather not use CoffeeScript.
- stanleydrew 16y agoChoices are kind of antithetical to rails's core philosophy of convention over configuration.
- jarin 16y agoI think it is requiring the user to make a choice that is antithetical. You can change pretty much all of the defaults in Rails.
- stanleydrew 16y agoAgreed, and that is indeed what I meant. Coffeescript has always been a choice in the sense that I could download the compiler and use the output in my rails project.
- sabat 16y agoIt will remain a choice. Rails doesn't obliterate choices, just makes it easier if you're willing to take defaults. On the other hand, replacements for default components (e.g. Rspec vs. default Test::Unit) are generally simple to drop in.
- jarin 16y agoRails is a pretty huge learning curve in and of itself, as most developers need to learn MVC, unit testing, migrations, activerecord, callbacks, filter chains, routing, erb, view helpers, partials, layouts, etc. Of course, all of this stuff makes your life easier once you learn it. I would even be down with making Haml and Sass the default, since most Rails developers seem to use them anyway. Scaffolds would give newbies a good starting point to work with.