Jon, this whole episode was precipitated by the fact that someone's app was broken by this behavior. See clifton's pull request here<https://github.com/rails/rails/pull/5329> .
On Mon, Mar 26, 2012 at 1:05 AM, dburry <[email protected]> wrote: > Thanks Ben for the thoughtful words. I agree wholeheartedly. > > The way this issue is being handled illustrates why many rails lovers > originally resorted to writing Merb, which was then borrowed from to > create Rails 3 when the rails guys finally came to their senses. It > also illustrates why one Russian guy recently got so frustrated at a > few core guys refusing to listen to the masses, that he 0day hacked > the rails repo, just to prove a point about why a certain decision was > so evil for rails app security. Please stop making the masses of > people who care about rails resort to such tactics to be heard. > > Dave > > On Mar 25, 10:49 pm, Ben Woosley <[email protected]> wrote: > > 2. Generally return true/false, but may return other values instead if > > there is a good reason to, such as the ability to conveniently provide > > pertinent information (The core lib's position, my position and the > > position of basically everyone else AFAICT) > > -- > 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.
