Ruby on Rails

Why it's ranked here

Lockstep versioning is the strongest argument here. One version string drives every sibling gem, so upgrading is a single decision instead of twelve compatibility bets, and the monorepo layout keeps a cross cutting fix inside one pull request. Against that, installing the full stack pulls in twelve gems plus a code loader, a task runner, a command parser and a REPL, and the declared floor is Ruby 3.3.1 or newer. Four database adapters each get a dedicated test task, so the database abstraction is exercised rather than assumed.

What's good

Components are built to survive outside the framework. The ORM, the model interfaces, the request layer and the view layer are each documented as usable standalone, and each carries its own gem specification, changelog and tests. The ORM documentation is candid about its own seams: it says you can drop to SQL for odd cases and that it will not replace your schema definitions. Contribution rules are stated plainly. Cosmetic patches are rejected, feature ideas go to the forum before an issue is opened, and changes to core Ruby extensions are pushed upstream to Ruby instead.

Tradeoffs

Convention over configuration cuts both ways. The ORM infers table and foreign key names from class names, so the mapping stays invisible until it guesses wrong. The development dependency list is long: three database drivers, several asset pipelines, cloud storage clients, image processing, four job backends. Testing is opinionated, using Minitest rather than RSpec, and the suite runs across multiple processes, which makes chasing one failure harder. Nothing here covers front end state management or a component model. The JavaScript that ships is a thin client for WebSockets, uploads and rich text.

How to use it well

Pick this when you are building a database backed product and want one team to own the whole request path, from schema to HTML, without assembling a stack from parts. It pays off most for small teams shipping data heavy applications that also need real time updates, mail and background work in the same codebase. Individual pieces are worth borrowing on their own: the ORM and the utility extensions run outside the framework. It gives you no front end framework, no mobile client, no API gateway, and it will not manage your infrastructure.

Observed

License

MIT, per MIT-LICENSE and every gem specification read

Language

Ruby, with small bundled JavaScript clients for the browser side

Install surface

RubyGems: one meta gem that pulls in the sibling framework gems

Interfaces

A command line executable shipped by railties, plus library APIs per component

Repository shape

Monorepo, each component with its own gem specification, changelog and tests

Database adapters

SQLite3, PostgreSQL, MySQL2 and Trilogy have dedicated test tasks

Test framework

Minitest run across parallel processes, no RSpec in the tree

Security reporting

Vulnerabilities routed to a published security policy, not GitHub issues