> First, Michael, the original pull request 
> (https://github.com/rails/rails/pull/5329) was opened by @clifton, whose app 
> was broken by this change.
> 

The author admits that that change is bad form anyway. I agree it's mildly 
annoying however unless we take position 1 in your list then there's *always* 
going to be stuff that breaks in his 'serialize to json' case.  The two 
languages are different and these things will happen.
> When valid pull requests and attempts at compromise are closed for reasons 
> which are clearly unpersuasive to a significant number of rubyists, by the 
> one core member who created of the issue, it makes me wonder. Shouldn't we 
> just settle this by openly choosing the best of the 3 options above, or some 
> as-yet unarticulated option?
> 
> 

The 'a significant number of rubyists' argument is a slippery slope.  You can 
drum up an internet army to bitch and moan about any change you'd like here, 
and there's always someone who thinks that it's a frigging TRAVESTY that the 
bike shed is blue.

To put it simply, there's no place to draw the line with niggly little pull 
requests like this and to consume the limited time of the community of 
contributors going back and forward over this is entirely.  This thread has 
already brought out some nutjob with a laughably incoherent view on history and 
an axe to grind.  These long bikeshedding threads serve only to feed the madmen 
with nothing better to do.  The negative side effects to the community of 
encouraging this kind of thing FAR outweighs the potential benefits of fixing 
'just this one thing'.

I'm sorry that someone's app broke, and I'm sorry that tickets were hastily 
closed in a way that came across as hostile or dismissive.  But to dwell on 
this further is worse.

--
Cheers,

Koz

-- 
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.

Reply via email to