Ruby on Rails
A full-stack web framework whose core design philosophy is convention over configuration and DRY (Don't Repeat Yourself). It includes built-in ORM, routing, and templating components and is widely used in web application development.
Core Facts
The convention over configuration philosophy was first popularized by the Ruby on Rails framework in 2004.
DHH is the creator of Ruby on Rails and co-founder of 37signals.
David Heinemeier Hansson (DHH) is the founder of Ruby on Rails.
Timeline (last 90 days)
The 2026 Ruby on Rails community survey results have been released, with only 4 points and 1 comment on Hacker News.
If the survey data shows that the proportion of young developers using it is rebounding, it may mean that Rails' built-in batteries strategy is regaining appeal; if it continues to decline, it means the community needs to seriously think about the issue of passing the torch.
Rails' community surveys over the years typically cover dimensions such as the distribution of Rails versions developers use, deployment solution choices, frontend technology pairings, testing toolchains, and developers' subjective evaluations of the framework's development direction.
Hotwire, through the HTML over the wire approach, lets developers obtain an interaction experience close to that of an SPA while writing less JavaScript, which is highly consistent with Rails' server-side rendering philosophy.
The downside cost of convention over configuration is a sense of magic; when the default behavior does not meet requirements, developers need to understand the framework's internal inference rules in order to override it correctly.
Rails' strategy of building in Solid Queue, Solid Cache, and Solid Cable has pros and cons: supporters believe it lowers the startup cost of new projects, while opponents worry that the expansion of the framework's boundaries brings lock-in effects.
In its evolution from 7.x to 8.x, Rails chose the path of subtraction and building in more parallel components.
JavaScript full-stack approaches (Next.js, Remix, etc.) have absorbed the rapid web application building scenarios that originally belonged to Rails.
The convention-over-configuration paradigm was popularized by Rails around 2004, and its core claim is that the framework presets reasonable default behavior for common scenarios, so developers only need to write configuration when deviating from the default conventions.
ActiveRecord is the ORM layer built into Rails, providing capabilities such as migrations, associations, chained query APIs, callbacks, and validations.
23 more timeline events
All Facts (20)
The convention over configuration philosophy was first popularized by the Ruby on Rails framework in 2004.
80%VerifiedDHH is the creator of Ruby on Rails and co-founder of 37signals.
75%VerifiedDavid Heinemeier Hansson (DHH) is the founder of Ruby on Rails.
65%VerifiedConvention over Configuration is the core design principle for which Ruby on Rails is renowned.
65%VerifiedShopify, GitHub, Basecamp, and early versions of Airbnb were all built on Rails.
65%VerifiedRuby on Rails has been available since its release in 2004.
65%UnverifiedGitHub创立于2008年，最初是一个基于Ruby on Rails构建的单体应用
95%UnverifiedThe Ruby on Rails framework gave rise to the early technology stacks of companies such as Twitter, GitHub, and Shopify.
60%UnverifiedThe "Convention over Configuration" principle was first popularized by the Ruby on Rails framework in 2004.
60%UnverifiedBehind the Omarchy project is DHH (David Heinemeier Hansson), the creator of Ruby on Rails.
60%UnverifiedTobias Lütke is a programmer-turned-CEO who built the initial version of Shopify using the Ruby on Rails framework in 2004 and was an early contributor to the Rails community.
60%UnverifiedActiveRecord is the ORM layer built into Rails, providing capabilities such as migrations, associations, chained query APIs, callbacks, and validations.
50%UnverifiedRails 8 introduced three database-backed default infrastructure components—Solid Queue, Solid Cache, and Solid Cable—corresponding respectively to the background job queue, the caching layer, and WebSocket broadcasting.
50%UnverifiedHotwire is the frontend approach led officially by Rails, consisting of two parts: Turbo and Stimulus.
50%UnverifiedRails' community surveys over the years typically cover dimensions such as the distribution of Rails versions developers use, deployment solution choices, frontend technology pairings, testing toolchains, and developers' subjective evaluations of the framework's development direction.
50%UnverifiedHotwire, through the HTML over the wire approach, lets developers obtain an interaction experience close to that of an SPA while writing less JavaScript, which is highly consistent with Rails' server-side rendering philosophy.
50%UnverifiedThe downside cost of convention over configuration is a sense of magic; when the default behavior does not meet requirements, developers need to understand the framework's internal inference rules in order to override it correctly.
50%UnverifiedRails' strategy of building in Solid Queue, Solid Cache, and Solid Cable has pros and cons: supporters believe it lowers the startup cost of new projects, while opponents worry that the expansion of the framework's boundaries brings lock-in effects.
50%UnverifiedIn its evolution from 7.x to 8.x, Rails chose the path of subtraction and building in more parallel components.
50%UnverifiedJavaScript full-stack approaches (Next.js, Remix, etc.) have absorbed the rapid web application building scenarios that originally belonged to Rails.
50%