Dear Rubyists: Shopify Isn't Your Enemy
Key topics
The author defends Shopify against perceived animosity from the Ruby community, sparking a discussion about the relationship between companies and open-source maintainers, with some commenters questioning the allegations and others praising the post's insight into the issues.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
52m
Peak period
3
6-8h
Avg / period
1.4
Based on 13 loaded comments
Key moments
- 01Story posted
Oct 9, 2025 at 10:20 AM EDT
3 months ago
Step 01 - 02First comment
Oct 9, 2025 at 11:12 AM EDT
52m after posting
Step 02 - 03Peak activity
3 comments in 6-8h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 10, 2025 at 3:14 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
“Yet, Ruby and Rails remain the default stack at Shopify, and the only reason for that is the CEO. Every Shopify employee knows that suggesting straying away from Ruby wouldn’t fly there. And I’m convinced that if it were anyone else at the helm, Shopify would have joined the long list of companies that attempted to migrate to something else and are now stuck with both a Ruby monolith and a ton of half-migrated micro-services in Java or Go.”
> I don’t know when their side of the story will come out, nor if it will come out at all, but I do hope it comes out soon and with receipts. Seeing so many good-natured and well-intentioned people get demonized like they have been over the last few weeks is depressing.
I haven't written Ruby professionally since 2019 (and don't have any plans to return to it currently), so my perspective on this is mostly that of an outsider who happened to be involved in the community for a few years in the past but otherwise doesn't really have much opinion about any of the organizations or people involved in all of the recent controversy. All that being said, it's hard for me to understand what the mindset is of authors of blog posts like this that attempt to provide context by providing extremely detailed history of events that involve the various personalities party to the current events right up until the actual controversy, at which point the only claims made are fairly vague allusions to there being more to the story with even a hint at what that might be. I understand the instinct to want to defend people you have good relationships with (or at least, have only had friction with in the past due around unrelated things), but at least to me, it doesn't really come across as anything other than an implicit attempt at damage control.
The grievances against Shopify seem pretty legitimate based on the only knowledge we have as outsiders. As far as I'm aware, the only concrete explanation of what happened that has been shared publicly is that they told RubyCentral that they either needed to take over the Github organization that owns bundler and the offline CLI RubyGems tool (not to be confused with the RubyGems.org package repository that RubyCentral did already own) and remove at least some of the specific external maintainers or they'd pull their funding. There have been proposed explanations for this around supply-chain security, but as far as I've read, no one has publicly stated a different set of events for what led up to the change in ownership of the Github organization, and without that, I don't think any amount of references to there being another side to the story will sound particularly convincing.
> at which point the only claims made are fairly vague allusions to there being more to the story with even a hint at what that might be.
The goal of my post was mostly to provide "character evidence".
It's not for me to relay accusations made by others that I can't substantiate myself. Some other people did that previously and that is what caused that massive controversy.
> The grievances against Shopify seem pretty legitimate based on the only knowledge we have as outsiders.
My whole post is about how these allegations are horseshit.
But since then, new information came out, you may want to read https://news.ycombinator.com/item?id=45530832, that may change your perspective.
I did read that article before seeing your response here. I honestly don't feel like it does much to change my perception of the events that led up to it. My understanding of the claims that you are describing as horseshit are that someone who maintained gem and bundler for years got intentionally pushed out after Ruby Central was threatened to have their funding revoked from Shopify if they didn't take over those packages and remove him. I had never heard of this maintainer before, but I have used bundler and gem before, so my perspective is that even if he was a problem and there was an argument that he should be removed, having one third party threaten another into removing him by forcing the change in ownership of the tools used by the entire community is an extremely myopic way of doing it. Doing an improper job of it that gave him an opening to potentially exploit his continued access is exactly the sort of thing that explains why you shouldn't go about forcing changes like this without adequate transparency and community consensus; instead of improving the security for the community, now a bunch of people who had never heard of the parties involved with this conflict need to be worried about the collateral damage. If you think someone is dangerous, it would make sense to be prepared for this sort of thing after you escalate your conflict with them.
In the absence of any other explanation about what actually happened, the only accounting of the events paints the change in ownership as at best reckless and irresponsible. I'd love to be wrong, but without anything concrete to explain why I shouldn't trust this, I can't differentiate between the reality we're in and one where the accusations are correct and the responses to them are being made in bad faith, and the simplest explanation is that it's because they're the same.
So you take the original allegations at face value, even though they only rely on second hand reporting of anonymous testimonies, yet you don't want to consider my post even though the standard of proof is the same.
Got it.
The problem with your post is that you're asking people to believe something without telling them what it is. I'd be more than willing to consider an alternate explanation of what happened but so far no one has been willing to share one. Regardless of your reasoning for withholding it (and the reasons of the others who apparently have knowledge of it), no one is going to be convinced of anything of anything by just asking people to trust blindly. At the end of the day, people are not going to believe there's some secret truth that explains everything about how Ruby Central and Shopify were acting if l in good faith; they'll need to be told what actually happened, or they'll quite understandably trust the people who don't seem to be trying to hide something.
The logical conclusion of this argument is that if you maintain a critical piece of infrastructure with a "large moat" you are apparently expected to live in poverty, or turn it over to a $2.68B revenue per quarter company because trying to extract $60k/yr of living expenses from rubygems is a bridge too far.
And I just don't buy all the framing that donating your employee's time is fundamentally different from donating money.
Is being monetized wrong? If so... Is there any REAL evidence? It's bizarre to talk about this WITHOUT evidence. Is it a witch hunt?
This story is bizarre on so many levels, I have no idea what's going on, but extraordinary claims require extraordinary evidence.
And, though I'm sure the author wasn't particularly concerned with his literary technique, this was all foreshadowed discussing the strained relationship with Tobi (maximalist vs nuance).
This is a very broadly applicable/generalizable blog post that I think should be read even if you don't care about the specific ruby drama going on.