Uniform architecture for 80/80
I believe that for 80% of cases of 80% of Rails applications there's no need to invent a wheel.
In the early years of Rails we had just one way to organize our code. Since we realized vanilla Rails way is not enough to handle complex cases, it is no longer the case.
Today we have an enourmous amount of approaches and techniques solving the same problem of code organization each in a slightly different way.
Two important statements:
- 80% of tasks in 80% of Rails applications are alike.
- Programmers are engineers, not artists.
If you agree with these statements, then you should agree that the majority of those approaches are not optimal. Engineers are seeking for a single optimal way of solving a specific task, and they stick to it, replicating it in all their new products.