Is Ruby Dying in 2026?
No — but it is not growing either. Ruby sits at #12 in the LangPop composite index with a score of 9.5, roughly half of where a top-10 language scores and a long way off Ruby's mid-2010s peak. The honest answer for 2026: Ruby stopped being a growth language years ago and has settled into a large, stable, well-paid maintenance market built almost entirely around Rails. That is a different story from "dying," and the data backs the distinction up.
Where Ruby ranks across all sources
The LangPop composite score draws from seven independent data sources. Ruby's per-source spread (week of July 12, 2026) is consistent — no source has Ruby dramatically higher or lower than its overall #12 rank, which is itself informative: a genuinely dying language usually shows a widening gap between its remaining community signal (Stack Overflow, GitHub) and its forward-looking demand signal (jobs, tutorials). Ruby does not show that gap.
| Source | Ruby position | Weight |
|---|---|---|
| GitHub activity Middle of the pack — Rails and its ecosystem gems are still actively maintained, not abandoned | #10 | 25% |
| Stack Overflow A smaller but still-active question base; matches an installed, maintained user base rather than new learners | #10 | 15% |
| Tutorial platforms Steady mid-pack enrollment — Ruby is still commonly taught, just not growing | #10 | 5% |
| Job postings Real, ongoing demand concentrated in companies with existing Rails codebases (Shopify, GitHub, and their ecosystems) | #11 | 20% |
| Wikipedia pageviews Public interest has cooled since the 2010s Rails hype cycle | #13 | 15% |
| Package registries *Proxy signal only — LangPop tracks npm/PyPI packages that mention "ruby", not RubyGems itself (not yet a tracked registry). Reads near-zero for any Ruby-ecosystem language for this reason, not because gem publishing has stopped. | #15* | 10% |
| Reddit mentions Reddit API access is not yet live for any language in the index (site-wide gap, not Ruby-specific) | n/a | 10% |
What actually happened to Ruby
Ruby peaked in popularity around 2015, carried almost entirely by Ruby on Rails' dominance of the startup web-framework market. Rails was, for most of the 2010s, the default answer to "how do we ship a database-backed web app fast." That era ended — not because Rails broke, but because the market it won got crowded. Node.js gave JavaScript teams a full-stack option. Django matured into a comparable Python equivalent. And the rise of React/Vue-driven frontends pulled a lot of new projects toward JavaScript-first stacks by default.
What did not happen is collapse. The installed base of Rails applications built during the 2010s is large, mature, and still generating revenue — and those applications need engineers who know Ruby. That is the maintenance-market story this article keeps coming back to: Ruby's new-project share shrank hard, but its existing-project demand did not follow it down.
Where Ruby still runs in production
Shopify
Shopify runs one of the largest Rails codebases in the world and has kept investing rather than migrating away — YJIT, the Ruby JIT compiler that meaningfully improved Rails performance, was developed at Shopify and merged directly into Ruby core. That is not the behaviour of a company planning to leave the language.
GitHub
GitHub itself was built on Rails and continues to run substantial Rails infrastructure. For a company at GitHub's scale to still be Rails-based is a standing counter-argument to "Rails doesn't scale."
Shopify's app ecosystem
Third-party Shopify apps, custom storefronts, and Shopify Partners development happen in Ruby/Rails — a commercially active ecosystem with direct revenue opportunities that did not exist for most other "declining" languages.
Developer tooling
Jekyll (static site generator) and Fastlane (iOS/Android build automation) are Ruby projects with wide adoption well outside the Rails web-app world — Ruby's scripting heritage keeps it relevant in developer-workflow tooling.
Ruby and AI coding tools
Ruby is well-represented in AI training data — Rails conventions are thoroughly understood by GitHub Copilot and similar tools, which generate idiomatic Rails code reliably. The AI era has not produced a Ruby-native machine-learning ecosystem the way it has for Python, but Ruby developers are integrating LLMs at the application layer through community gems wrapping OpenAI and Anthropic APIs. There is a plausible case that AI coding assistance partly recaptures Rails' original productivity pitch — fewer lines of code, strong conventions — which may help Ruby's case in maintenance contexts even without new-project growth.
The honest job market picture
Ruby job demand is stable but not growing. The market is overwhelmingly maintenance-focused: companies that built on Rails in the 2010s continue to hire Ruby engineers to extend and operate those systems, rather than to start new ones. This produces an unusual hiring dynamic — the volume of open roles is modest compared to Python or JavaScript, but senior Rails engineers who can navigate large, complex, years-old codebases are well-compensated relative to how few of them there are.
The practical read for a career decision: learning Ruby as your first or only language in 2026 is a narrow bet — the new-project market is small. Learning it as a second language because you are targeting a Rails-heavy employer (Shopify, GitHub, or the many mid-market companies still running Rails) is a much more defensible, well-compensated bet.
What this means for you
Learning to code
Ruby is not the language to learn first in 2026 if your goal is maximizing entry-level job options — Python and JavaScript have far larger beginner-friendly markets. Learn Ruby specifically if you have a concrete reason: a target employer runs Rails, or you are drawn to Rails' developer-experience philosophy for a personal project.
Already a web developer (JS/Python/PHP)
Ruby is worth learning if you are targeting Rails-heavy employers or e-commerce/Shopify ecosystem work. The concepts transfer quickly from any dynamic-language background; the main investment is learning Rails' conventions, which are well-documented and AI-tool-friendly.
Evaluating Ruby for a new project
Ruby/Rails remains a legitimate choice for a database-backed web app where developer productivity and convention-over-configuration matter more than hiring-pool size — small teams, internal tools, and founders who already know Rails well. It is a weaker choice if you need the largest possible hiring pool or a JavaScript-native full-stack story.
Hiring engineers
Expect a smaller candidate pool than for Python or JavaScript, concentrated among engineers with real Rails production experience. Compensation for senior Rails engineers is often strong precisely because supply is constrained relative to the size of the installed Rails codebase you need maintained.
The 12-month outlook: stable, not resurgent
Nothing in the current data points to either a Ruby collapse or a Ruby comeback. The forces that ended Ruby's growth era — Node.js and Django maturing into credible full-stack alternatives, JavaScript-first frontend frameworks pulling new projects toward JS-native stacks — are structural and are not reversing. Equally, nothing points to Rails codebases disappearing: Shopify and GitHub's continued investment (including funding Ruby core performance work) suggests the maintenance market has years of runway left, not a few.
Our assessment for 2026: Ruby holds around #12, essentially flat, for the same reason it has held there for a while — a real, durable maintenance market with no new-project growth engine behind it. "Dying" implies a trend heading toward zero. Ruby's actual trend is closer to a plateau, and plateaus can last a very long time when a company the size of Shopify is actively paying to keep the language fast.
Ruby's current score, rank history, and source breakdown are available on the Ruby language page. Compare Ruby against any other language using the comparison tool.
Compare languages → Open the LangPop Comparison Tool
Compare now →