Rails for everything

Original Article ↗ Hacker News Discussion ↗

Rails “omakase” & developer experience

  • Many praise Rails’ convention-over-configuration for fast CRUD, validation, flash messages, storage, jobs, and generators.
  • Built-in features (ActiveStorage, ActionText, Solid Queue/Cache/Cable, basic auth) are seen as strong advantages for solo devs and small teams.
  • Some warn against blindly enabling everything (Turbo, CI, tests) for throwaway MVPs; defaults can be overkill for tiny experiments.

SQLite, Solid stack, and litestack

  • Rails 8’s SQLite-first posture is welcomed for small apps and easy sharing (e.g., Docker + SQLite).
  • Critics note SQLite’s migration limitations (e.g., adding constraints) and lack of PL/stored procs, calling Postgres more suitable for long-lived apps.
  • litestack is discussed as an SQLite-based alternative providing queues/caches; some say Rails 8 now covers most of that; litestream confusion is clarified.

Auth, admin, and “batteries”

  • Many value inbuilt auth and wish Rails had a first-class admin akin to Django Admin; current answers are scaffolding, admin-generator gems, and commercial/admin gems.
  • Debate over Devise: some find it overcomplicated post–Rails 8; others emphasize its hard-won security and support for OAuth/2FA and advise against rolling custom auth.
  • Tools like authentication-zero and admin templates are mentioned as lighter alternatives.

Hotwire, frontend, and mobile

  • Hotwire/Turbo/Stimulus are praised for avoiding SPA complexity; some struggle with the mindset shift but find it powerful once they stop thinking in “React-style components.”
  • Rails + Sitepress is used instead of static generators to keep “static” sites easily extensible.
  • Hotwire Native (Strada) is emerging for iOS/Android, seen as good for many flows but not all highly polished mobile UX cases.

Comparisons with Django, Go, and others

  • Django: seen as similarly “for everything,” with stronger built-in admin and Python ecosystem; Rails seen as more opinionated, test-focused, and DRY/magical.
  • Go: widely liked for services/CLIs, but many feel the “no big framework” culture leaves a gap versus Rails/Django for full-stack apps.
  • Spring/ASP.NET: some claim comparable productivity once mastered; others see Rails as far leaner and less boilerplate-heavy.

Performance, security, and longevity

  • Ruby performance has improved (YJIT), but most argue web bottlenecks are elsewhere (I/O, APIs).
  • Rails defaults are viewed as security-conscious; repeated GitLab CVEs are attributed more to application quality than the framework.
  • Multiple reports of multi-version Rails upgrades and decade-long apps suggest Rails remains maintainable and far from “dead,” though market popularity varies by region and stack.