zlacker

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+(OP)
> 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+R2
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+95
> 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.

>>bradge+(OP)
Ruby's status of having, like, two companies that are big and known to use Ruby (Shopify and 37Signals) is the reason why this was allowed to happen (three if you include Github, but my understanding is that its used less-and-less there). I have doubts that anyone could name another company or group most people have heard of using Ruby in any significant capacity. Its a dying language that does not have the legs to survive this drama.

>>827a+c9
Stripe, AirBnB, Instacart, Zendesk, Kickstarter, Mastodon, and if I remember right Coinbase was originally Rails as well.

>>WA9ACE+Ud
Twitter also

>>gleenn+nh
Twitter famously eliminated as much ruby as practical from their codebase.

>>WA9ACE+Ud
Many if not all of these companies are, to my knowledge, companies like Github which might still have some legacy parts of their system running Ruby, but aren't building significant new code in Ruby; and if they do have Ruby, are trying to reduce its prevalence in their system.

>>827a+Dm
You're badly misinformed (or are intentionally spreading misinformation).

>>leakyc+R2
>Ruby will be lucky to have a shadow of the community left after this.

Maybe? This feels like an extreme statement with too much certainty at this point.

>>3by7+Nq
Your claim would have more standing if 1) it made sense vs. the news and recent yearslong turn away from Ruby development, and 2) if you included any sources or information other than "nuh uh"

>>3by7+Nq
I can vouch for at least one of those companies especially if we go by the "trying" bit of the GP.

>>mvdtnz+Qi
Had to kill the failwhale.

>>3by7+Nq
Square was originally a single RoR monolith. We spent a decade burning it to the ground with a Java and Go microservice architecture.

Some product surface area remains Ruby, but Ruby was chased away by most teams.

Square brought in a lot of Xooglers over the years to lead the transition, so you see a lot of Google tech: protobufs, gRPCs, at one point a pre-Kubernetes Borg clone, etc.

>>WA9ACE+Ud
GitLab too: https://gitlab.com/gitlab-org/gitlab

>>leakyc+ov
'Download Github and look at the code'?