This is why we have things like Rails. I can instantly tell if a project was done by someone who loves rails or someone who just does it. If someone understood what it wants, everyone after them will be able to instantly find and understand the code.

Pure Ruby on the other hand... I've read some scripts that are as hard to parse as perl for me, some others that could be a copy of the official tutorial.

What does that mean?

There is a continuum between a language that's very restrictive and forces you to do things one way (I'd think of Go as one pole here), and a language that provides countless redundant ways to do things without clear advantages over another, and in my opinion Ruby goes too far in the direction of giving you too many ways to do things. The disadvantage of that is that it works against uniformity in a project and makes each file its own little puzzle.

> too many ways to do things

If there are many ways, then there is no obvious way, but then the "if" part of what you said does not apply.

I think your thought is much better captured by "if everything is possible, nothing is obvious".

You’re probably right. I was just thinking it is not “obvious” what code does after the fact.