| Sometimes trolling is not false. You're making broad generalizations about the ruby community and it's members, many of whom do not fit your stereotypes. His generalizations fit well enough to include the dev teams of the core package management system and the by-far predominant application framework. As broad generalizations go that's a pretty effective reach. Has the compromise of Rubygems been an event of such massive proportion that it effects all ruby devs and those who rely upon them? Yeah. Yeah. Do things need to be fixed? Yes. Yes. Can these things be fixed within the Ruby community? Yes. Woah, hold your horses there. Can they be fixed within a Ruby community? Yes. Can they be fixed within the community as it now stands, with its present culture and practices? I would hesitate before answering yes. But please, stop being an asshole while doing it. Turned out Walter was right, in the end. She did kidnap herself. |
I don't begrudge people being right (although, I also don't happen to think that Mr. Potato there is totally correct). I do however have a problem with people being jerks.
Moreover, being right does not give someone license to be a jerk either.
-----------------------------
As for the substance, yeah I do think there are ways to secure Ruby gems better, and I think that given the way the Ruby community is organized (since it's not a monolith), there are paths forward that can be organized and implemented by smart and interested rubyists, and those paths can and will be adopted by the bulk of developers who aren't as engaged in the Ruby ecosystem.