Why we use Ruby on Rails to build GitLab

This post details the rationale behind choosing Ruby on Rails for building GitLab, highlighting its strengths in enabling high-quality functionality, consistency through best practices, and a rich gem ecosystem. It also discusses challenges related to Ruby's production performance and memory usage, and how these are being addressed by rewriting critical parts in Go (leading to Gitaly) and pursuing multithreading. The post emphasizes how Rails' opinionated structure aligns with GitLab's mission of enabling everyone to contribute by making the codebase more accessible to new developers.