Products · Product
Ruby on Rails
Raised as a usability problem by 207 people on Hacker News over 20 years (2007–2026), in 192 threads.
No issue was raised by at least 3 people in 3 threads this year.
- 1
- 2
- 3
- 4
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
Every issue, all time, most people first
Internals are so tangled developers can't work out how they workUnreviewed
20072026- Refactoring Rails code is far more painful than in Rust2025-02-23
- Rails and RSpec docs are unclear, so developers struggle to figure out how to do things2024-12-24
- Framework abuses Ruby's flexibility, making many things hard to debug2023-12-25
Setting up Rails on Windows is painful for beginnersUnreviewed
20072026- Ruby/Rails is annoying to use on Windows2022-08-05
- Setting up local Ruby environment is hard and can break the machine2021-12-17
- Gems needing Linux build tools or POSIX break the setup on Windows2016-10-16
Implicit magic makes framework hard to track over timeUnreviewed
20072026- Hard to find anything in large Rails codebases due to magic2025-05-03
- Everything is implicit, so it is horrible to find out what code does2024-08-14
- Steep learning curve and implicit magic make the framework frustrating to learn and maintain2024-08-02
Hard to tell where methods come from when macros generate codeUnreviewed
20072026- Hard to find where things are declared due to convention over configuration2026-07-13
- Hard to tell where methods come from when macros generate code2025-10-17
- Implicit conventions hide config, so it's hard to find and grep2025-10-05
When implicit conventions break, it's hard to tell whyUnreviewed
20072026- When implicit conventions break, it's hard to tell why2020-05-05
- Hard to learn; requires a large body of conventions before productive use2019-01-10
- Implicit conventions leave beginners helpless and hard to change when defaults don't match needs2017-05-06
Outsiders struggle to understand and fix messy codebasesUnreviewed
20072026- Framework lets codebases become a mess, and outsiders struggle to understand and fix them2025-06-12
- Constant workarounds needed for framework imperfections, frustrating daily developer experience2016-07-12
- Can't tell what one-line framework code does, making bugs hard to debug2016-05-23
Upgrading Rails 2 to 3 was so hard a new app was neededUnreviewed
20072026- Commenter finds Rails apps impossible to install and get running, despite being inexperienced2015-09-18
- Upgrading Rails 2 to 3 was so hard the commenter had to start a new app2014-01-27
- Commenter got tired of the Rails routes file, their biggest complaint2012-01-16
Error messages are cryptic and hard to decipherUnreviewed
20072026- Misleading or missing error messages force debugging for minor problems2019-02-01
- Hard to tell which line caused an error, debugging views with helpers is difficult2012-10-09
- Cryptic error messages and setup problems cause hours of googling and fixing2012-09-06
Slow boot-up makes test runs slow, breaking flowUnreviewed
20072026- Rails boot-up makes test runs slow, breaking the developer's flow2013-03-05
- Ruby application startup is so slow that users wait far longer than expected2012-12-29
- Rails takes seconds to run rake -T, forcing the user to seek faster alternatives2012-09-13
Tangled gem dependencies and poor version documentationUnreviewed
20072026- Setting up the debugger was very difficult, needing a specific gem patch version2019-05-29
- Gets lost in Homebrew, PATH, rvm, gemsets and version setup while following tutorial2016-08-12
- Gem dependencies were tangled and documentation for version numbers was poor or missing2012-12-09
Overused cleverness makes debugging harder than necessaryUnreviewed
20072026- Easy to make a mess and hard to debug2026-05-27
- Overused cleverness made debugging far harder than necessary2023-10-20
- Hidden complexity behind friendly abstractions makes debugging hard when things break2023-09-12
Add-on gems work behind the scenes, hard to understandUnreviewed
20072026- Code is hard to follow because methods and attributes are generated implicitly from gems2023-01-11
- Beginners struggle with sparse docs, skipped steps in samples, and broken gem updates2014-05-18
- Add-on gems do work behind the scenes, making them hard to understand past tutorials2013-05-23
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Hard to find where things are declared due to convention over configuration2026-07-13
- Easy to make a mess and hard to debug2026-05-27
- Generated app has dozens of files and lacking guidance on environment setup2026-03-12
- Main page elements auto-cycle too quickly, making them hard to read or interact with2026-01-22
- Page accidentally scrolls horizontally on iPhone, making it hard to scroll down2026-01-21
- Magic generators break opaquely and are hard to debug when something fails2026-01-02
- Hard to find where things are defined and how data flows2025-11-08
- Hard to tell where methods come from when macros generate code2025-10-17
- JavaScript dependencies are tricky and painful to integrate across Rails versions2025-10-16
- Implicit conventions hide config, so it's hard to find and grep2025-10-05
- Dev environment setup fails when compiling dependencies, making installation a constant nightmare2025-08-13
- Hard to trace where methods come from and lacks IDE autocomplete as the codebase grows2025-06-15
- Framework lets codebases become a mess, and outsiders struggle to understand and fix them2025-06-12
- Hard to find where a method is defined in large codebases2025-05-03
- Hard to find anything in large Rails codebases due to magic2025-05-03
- Refactoring Rails code is far more painful than in Rust2025-02-23
- Can't find where a class is defined because of auto-loading and generic names2025-02-03
- Rails and RSpec docs are unclear, so developers struggle to figure out how to do things2024-12-24
- Docs scattered across guides, API references and Turbo/Stimulus; hard to know idiomatic usage2024-12-17
- Silent behavior changes in gem methods and undocumented options are hard to discover2024-12-02
- Can't find instructions for using the beta or running bin/rails in the container2024-10-17
- Each object spans three files, so understanding one thing means switching many tabs2024-09-23
- Everything is implicit, so it is horrible to find out what code does2024-08-14
- Can't tell from reading code what objects and behavior actually are at runtime2024-08-03
- Steep learning curve and implicit magic make the framework frustrating to learn and maintain2024-08-02
- Hard to tell where variables and functions come from, causing confusing bugs2024-08-02
- Hard to discover relationships between code; searching strings is failure-prone without types2024-08-02
- Hard to learn because file locations and translation paths are implicit and fail silently2024-05-18
- Framework abuses Ruby's flexibility, making many things hard to debug2023-12-25
- Rails behaviour seems to appear from incantations, hard to trace or explain2023-12-24
- Projects need constant manual patching of libraries and dependencies just to build and run2023-11-13
- Overused cleverness made debugging far harder than necessary2023-10-20
- Can't find dependencies from the code and hard to debug when it breaks2023-10-06
- Hidden complexity behind friendly abstractions makes debugging hard when things break2023-09-12
- Migration docs are sparse, advanced features undocumented, and parameters confusingly mixed2023-09-12
- Needs constant lookups; defaults and setup steps don't work as expected2023-05-22
- Hard to know which methods exist; docs lack examples and return types2023-05-13
- Too much implicit magic makes it hard to tell what's happening2023-05-13
- Verbose, hard-to-read docs with unclear transitions; reader can't tell what a sentence means2023-04-30
- Steep learning curve; easy to start but hard to write maintainable code2023-04-29
- Hard to tell where a method or macro comes from when tracing code2023-04-07
- Pages load the view first and then the data, making them slow to load2023-02-13
- Code is hard to follow because methods and attributes are generated implicitly from gems2023-01-11
- Docs recommend scaffolding that experienced developers consider a stunt, confusing learners2023-01-05
- Easy to write slow code and hard to write good code2023-01-04
- Custom DSLs make code hard to read once you stray from defaults2022-12-31
- Having types in a separate file is inconvenient for developers2022-12-20
- Advanced tasks require unwinding hidden magic; docs are bad across versions2022-12-15
- Arel queries are so unreadable that developers needed SQL comments to understand them2022-10-15
- Ruby/Rails is annoying to use on Windows2022-08-05