[spleen]

Rails is more than good enough - it is a framework fine tuned for productivity and quick iterations.

However, convention over configuration means quicker delivery for small(er) teams, but more discussions once more opinionated developers join.

[creativeembassy]

Hard disagree. "More discussions once more opinionated developers join" is universally true regardless of which frameworks/philosophies you start with. The point of convention being more important than configuration is that it reduces those conversations, because you can rely on the conventions as a default.

If an opinionated developer thinks a different configuration is better, then that helps form the conversation immediately. Everyone is already familiar with the convention, so the discussion only needs to inform everyone about the pros/cons of the alternative.

[spleen]

Point taken. I was actually referring to concepts that do not come out of thr box with Rails.

For example, it promotes use of concerns, which can easily go out of control. Then other people come with singletons, interactors or service objects.

Or, like Minitest, which is fine to begin with, but the sooner you switch to RSpec, you will be better off in the long run.

In my experience, these kind of tooling options tend to fire up almost religious discussions.