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

@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.

@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.