zlacker

>>bradge+(OP)
I wasn't expecting such a nice writeup. Worth a read.

The Ruby community has been eating itself alive since almost the beginning, but it is sad to see the short-sighted destruction of trust and connection that this has had.

>>leakyc+U1
How has it been “eating itself alive”?

>>bradge+sm
Ruby promised programmer happiness and delivered programmer warfare.

Predating the current hostile takeover: •••the vitriol directed at early critics like Zed Shaw •••mysterious departure of _why the lucky stiff •••the contentious Code of Conduct •••DHH •••uneasy truce after the toxic tribalism of the Rails vs. Merb

There's more, but the linked article can send you down more interesting rabbit holes than more bullets on my list

>>leakyc+Bq
There’s been a ton of that, yes, but for most people who are building applications and websites with Ruby, it’s been stable, productive, and prosperous.

>>bradge+us
> How has it been “eating itself alive”?

> There's been a ton of that, yes...

What are you saying - because some people got rich off Ruby, it's OK that those things happened?

Clearly not - Ruby will be lucky to have a shadow of the community left after this.

>>leakyc+lv
No, I'm saying there's a lot of people who won't even know this happened. Fewer will know that it happened, but they'll view it as a scenario where the ends justify the means.

I'm on the record saying RC did a poor job rolling out these changes and treated the maintainers poorly.

There will be a lot of amazing Rubyists that leave, which is terrible, but it won't be "the shadow of a community left" because there's way too many people who depend on it to feed their families.

>>bradge+Dx
> No, I'm saying there's a lot of people who won't even know this happened.

In the world of "I'm sorry to that man" this seems like a given about literally everything.

Not knowing something happened is called being uninformed, and it doesn't change things or make the person right just because they don't know about something that occurred.

> There will be a lot of amazing Rubyists that leave

We agree. Listen, WebObjects still has a somewhat active community. Ruby's community won't be helped by recent events, but recent events happened because the Ruby community has been backstabby for a long time and no one has stopped it because there's too much money to be made in the meantime to care about things like people.