Dave Copeland 
Reason # 467 to not rely on software produced by 37 Signals:
https://github.com/hotwired/turbo/issues/1456
My only surprise is that David Rails didn't just post a picture of the fuck you slide and actually wrote a response
James Jefferies@davetron5000 what an absolute turnip… be grateful serfs!
ben@davetron5000 this is sort of my concern with stimulus too — I prefer it to the alternatives that I know of but the development direction is entirely at the whim of one individual. Even if we ignore the non-technical reasons to avoid his projects, there’s a clear pattern of development direction being driven by his whims.
Ilya Demukh@davetron5000 Ugh. „Open source is a gift” analogy is the worst. Why even bother having issues and prs enabled in a repo then?
Jason Garber@davetron5000 …was his written response "fuck you" or
@jgarber Ha, it was definitely "did you just tell me to go fuck myself?” - basically open source is a gift, enjoy it, we aren't fixing this issue, issue closed
@davetron5000 real "sounds like you told me to go fuck myself" vibes
@davetron5000 Literally last week, I was updating dependencies and ran headfirst into this gem's and accompanying Node package's poor maintenance.
The GitHub releases link to diffs which are utterly useless. Code just… appears? A close look at those diffs also shows mismatched version strings between the Git tag and the code itself.
Like… from whence do these changes land in the project?
Konnor Rogers@jgarber @davetron5000 OH I can tell you this!
So basically they release a new version to NPM here: https://github.com/hotwired/turbo
and then they go to the gem here: https://github.com/hotwired/turbo-rails/blob/main/package.json#L22-L23
and then they update the `package.json` to contain the new version of `@hotwired/turbo` and then they run the build through rollup and commit the new changes from running the rollup build 🙃
so the diff on `@hotwired/turbo-rails` is basically the result of running Rollup on `@hotwired/turbo`
@konnorrogers @davetron5000 oh good grief 🤦🏻♂️
(Thank you for the links, too! 😅)
Bradley Schaefer@davetron5000 Why isn’t it maintained more like Rails, where it is possible to make contributions for things outside of what 37signals uses it for?
There’s no need for dhh having a chip on his shoulder about people wanting to be able to make positive contributions to a project used far more widely than his business. If his attitude was like this when he started Rails, nobody would use it. He’s gotten so sour and anti-community
@soulcutter It may be just as simple as that the actual creators aren't in 37 signals any more, so they just don't put people on it to maintain it - I can't see him ever wanting to maintain coded he didn't write, so it just sits there until, I dunno, Rails 10 when it gets replaced according to the Rails Front-End Solution Cycle
Mike Perham 
@davetron5000 is there a term or phrase for open source code that no one can change? A tarball of bugs?
Caleb Hearth 
@getajobmike @davetron5000 “gift” apparently
Tom 🇪🇺🇺🇦🇩🇰🇬🇱🏳️🌈🏳️⚧️@davetron5000 agreed, however: the endless charade of “is this still maintained” is tiring. It happens on almost every repo.
Sam Stephenson@davetron5000 who could have possibly seen this coming? (also, did you know “gift” means “poison” in Danish? https://glosbe.com/da/en/gift)
Kasper Timm Hansen@davetron5000 fun fact, gift means poison in Danish. So it puts another meaning to "it's an open source gift"
Ryan Bigg@davetron5000 @getajobmike 37 signals abandoning an OSS project? Must be a day ending in Y.
Pawan Dubey@davetron5000 the community should fork it imo. I think any for-profit company will eventually reach a state where OSS maintenance is not their priority.
Robby Russell@davetron5000 “Is Turbo in maintenance mode?”
That’s a loaded question… and that’s kind of the point.
It assumes something’s wrong before anyone can even respond. Which makes all the debate about how it was handled feel a little silly.
Can we all agree this wasn’t a GitHub issue worth keeping open on any of our projects?
@robbyrussell It’s a closable issue, but I don’t see that as a loaded question at all. There’s reason for concern documented in that issue, and I’m not surprised anyone would genuinely want to know its status for the purpose of knowing whether or not to attempt to contribute to it, or even use it at all.
It was well-written and not in bad faith or snarky.
Paweł Świątkowski@robbyrussell no, we cannot agree on that. And If there is some doubt, the reply from DHH proved it was a right question to ask. @davetron5000
@robbyrussell Seemed like an honest ( & good-faith) question, given that it's in Rails and does not seem to be actively maintained. To be fair, the OP got a fast answer ("no”). This all seems reasonable and for me, it's a reason to avoid using that library/understand the risk that bugs may never be fixed. Had the same thought when he said at Rails World that 37S would change things however/whenever they liked. It's their code, so fair enough, but that creates a risk that should not be ignored.
Trevor Bramble@davetron5000 "I've made a fix for this because it's broken." "Yes it is. You're welcome."