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
DHH aside, most of this drama was over a decade ago.

>>jamesg+ry
"Actually, the Ruby community ripped itself apart a decade ago and has never changed and still suffering from the consequences except with the recent thing with the founder" is not a strong argument

>>leakyc+JA
No, but listing things that happened over the course of over a decade, some of which are well resolved and others (like why’s leaving) are questionable how they’re an indication of drama.

He left public programming, including Scratch, entirely.

>>tyre+MJ
> things that happened over the course of over a decade

Bad things happening to contributors year after year for a decade shows a toxic community that doesn't change even over a long period of time

The latest harm is just the continuation of what has been happening since the beginning

> some of which are well resolved

Resolved? Decisions were made, but the tensions were never resolved and people were hurt.

> He left public programming [...] entirely.

Yeah. That's what happens when someone is destroyed after years of their hard work is treated like nothing.