4 ms·
But fundamentally you've assumed malice where there was in fact a simple error. No, he assumed incompetence, which you seem to be intent on proving by continui
by _pius 17y ago
But fundamentally you've assumed malice where there was in fact a simple error.
No, he assumed incompetence, which you seem to be intent on proving by continuing to attack him and give this non-apology apology.
Had you taken a few minutes to check before doing this, we'd all have been better off.
Or you could've resolved this a week ago had you had a more mature process. The guy laid out the issue, presented a fix, and e-mailed you and the rest of the Core Team several times. How many more "few minutes" does he need to take before it stops being his fault in your opinion?
Stop attacking the guy, it's really poor form. Just admit you guys screwed up and move on.
- jrockway 17y agoStop attacking the guy, it's really poor form. Just admit you guys screwed up and move on. Sounds like Zed's analysis of the Rails community is still correct.
- _pius 17y agoAs someone who loves Rails, I'd hate to think that.
- zcrar70 17y agoYup - I'm amazed. The Rails community has gotten some flack for this kind of issue before, but rather than listen to the criticism and learn from it, they make the same mistake over and over. It's as if they feel that Rails is a direct product of their personalities, and that because Rails is so successful, anything they do is vindicated by that success. That's just the wrong approach.
- gommm 17y agoAnd this is why I loved merb and I'm still not sure the merge was a good thing....