Ruby Central's Destructive Legacy

Ruby Central — the nonprofit long tied to the Ruby programming world — is being accused of tearing apart the very community it was supposed to support, and the comment section is serving grief, suspicion, and blunt one-liners. The article lays out a brutal scorecard: conferences gone or cut back, key open-source projects moved elsewhere, major contributors gone, board members gone, directors gone, and sponsors disappearing and reappearing in a haze of alleged conflict questions. In plain English: people who helped keep Ruby’s app store and toolchain running say they were pushed out, and many readers sound less shocked than exhausted.

The loudest mood in the comments is basically “this is heartbreaking, but also how did it get this bad?” One of the shortest replies — “Tragic” from orta — landed like a tiny tombstone. Others went straight for the messy stuff, with jameskilton asking the kind of question that makes every scandal juicier: whether someone ever explained “trying to sell access” to site traffic logs. That’s the sort of accusation that instantly turns community drama into popcorn reading.

Then came the bigger existential panic: dzonga argued Ruby keeps denying reality, saying the language itself is getting better while the wider scene keeps sliding and clinging too hard to Rails and its famous personalities. Not everyone was doomposting, though: baggy_trough pushed back by saying Bundler and RubyGems are being maintained “ably, if not better,” suggesting the tools may survive even if the politics are on fire. The result? A classic tech-community split between “this is a disaster” and “the code is fine, the adults are not.”