I think it is off by default implicitly in all environments and the line in production.rb is a hint to turn it on. IIRC, it hints or warns that you would have to write thread-safe code to begin with and to use this carefully. Since most people do not write thread-safe code and doing so is the exception vs the rule, then this setting makes sense to most I have talked to. My opinion.
- Ken On Aug 12, 2011, at 8:40 AM, Rodrigo Rosenfeld Rosas wrote: > One of the things I love in Rails are the good defaults. Now that jQuery is > the default Javascript framework it got even better! :D Maybe sometime Rspec > will get there too ;) (Just kidding - although I prefer Rspec, I don't want > to start this discussion) > > But one thing that has always bothered me is why config.threadsafe! is > disabled by default in production.rb. > > This seems really odd to me. > > Could someone explain me the reasons behind this decision? > > Or, is it time for changing this default? > > Best regards, > > Rodrigo. > > -- > 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.
