If you write Ruby for a few years, and then you "go back" to other languages, you will groan. That's not to say that some other languages do not have things that we wish Ruby had, but often those other things would not really fit well with Ruby.
Nothing is perfect from every angle. But writing Ruby can be a joy for some of us.
I'm going to edit this: much of this is rails, we know why that is, so apologies to rubyists
It's no accident that it's named after one of the rarest gems in nature. This philosophy of craft and beauty is thus instilled within the community and gets carried forward.
Ruby is still a great programming language, but it really needs to intensify the effort to get out of the pit-of-decline.
The languages that have supplanted it haven't succeeded by being excellent. If excellence won't do it, what should "Ruby" do?
It's fundamentally a "we want workers to be interchangeable cogs" motivator; it's a deprofessionalizing move that's against the interests of all programmers per se. Managers can repeat it, but there's no good reason for developers to do anything but resist it where we can.
The other side of this for developers is that the places where "everyone knows X" precludes all non-X options are actually signaling loudly that they don't much value developer autonomy. That's a useful signal worth attending to when applying for jobs.