I'd argue the issue is better acknowledge in ruby than in many other popular languages, which just assume having few options means everyone can mostly code as t

I'd argue the issue is better acknowledge in ruby than in many other popular languages, which just assume having few options means everyone can mostly code as they want from there. Sister comments are pointing to rubocop which mostly makes it a solved problem. I'd add that having multiple potential ways to do things, and being able to also favor a specific way through linting is very powerful. You can actually choose the best option for your current project and enforce it, while choosing a different tradeoff for another project and still enforce it there. And you still can opt-out of the rules on a case by case basis in a standard way.