zlacker

If you don't realize the overlap in the Rails and Ruby on Rails community, I'm not sure what corner of the Ruby world you've been hiding in.

Someone can shush away any behavior if they want, like you have done. Feel free to provide an alternate history or context for the current Ruby community upheaval if you want, but just dismissing the problems of the past doesn't help anyone.

>>leakyc+(OP)
I'm not dismissing the problems of the past. I just don't think they were as big problems as you make them out to be. It's not like I wasn't around or unaware, I just didn't let it bother me - and was happy with how things were developing despite some arguments around the fringes as in any community.

> I'm not sure what corner of the Ruby world you've been hiding in.

I did say that I haven't been involved for the past dozen years. Before that I was definitely there when Rails burst onto the Ruby scene and its early years. I realize the overlap but they were still pretty distinct -- though maybe that's changed in the past decade.

>>insane+p7
"it didn't affect me so I didn't care" is a common and valid feeling up until you are aware of what is happening

I developed with Ruby from the beginning and loved Ruby on Rails for many reasons. The community's backstabbing nature and callousness toward people who put a lot of work in was not something I ever admired and it's led us here.

>>leakyc+89
You’ve made a lot of comments in this thread, and they come across far more subjective than objective. For people who have just been getting along and making things, they’re unlikely to be all that persuasive.