From Ruby to Crystal: A Quick Look

In my experience, StackOverflow rarely to ever comes up when I am looking for solutions to Ruby issues, while I often visit it for other things.

That might very well be a better explanation for why it doesn't appear high on the list for Stackoverflow. I'm not saying it's wrong. I'm saying there's no reason to assume StackOverflow's audience is unbiased and representative. It doesn't rate on my top 10 list of places to go looking for solutions to Ruby issues.

> and since there's clearly already an exodus out of Ruby and into other technologies like TypeScript and Python

I haven't seen anything of that supposed exodus. The few Rubyists I know that have stopped using Ruby have moved on to things like Elixir, not TypeScript or Python. I find that an extremely odd claim to make.

TypeScript to me is a total non-entity - I don't know anyone doing TypeScript anywhere. Not saying it's not popular, just that wherever it is popular is entirly outside of the sphere I work in. Python I come across, but again as a demonstration of how little our personal anecdotes mean: I see far more people starting Ruby projects than Python projects, and most of the places I come across Python, it is grudingly when working with third party code. At the same time I'm fully aware that there are niches where Python is far better represented than Ruby, but they don't often intersect with what I do outside of machine learning projects.

Because hard pull requests don't necessarily mean wider adoption. It gets down to which projects are represented on GitHub v. other platforms and those projects' source management philosophies.

GitHub is (or was, at some point) written in Rails and attracted the Ruby community early. Rails is developed on GitHub, as are many other major Ruby projects, including the Ruby language itself.

Python is hosted on its own Mercurial repository (though it is shifting to GitHub later this year) and that community never had the tribal draw to move its development from things like mailing lists into GitHub. Patches are still handled on the Python bug tracker, etc.

As for individual project source management, some projects will have all contributors with their private fork and have them make individual pull requests as part of the code review process, some will give a core of contributors direct access to make raw pushes, and so on.

Because of not every project uses GitHub and because GitHub's unmanaged pull request object is not a reliable unit of measurement, it's better to trust a survey that directly reflects real-world observances than to make extrapolations based on an unreliable metric.