Ruby's Creed
Allowing @1 and @2 instead of |a, b| is a horrible change to Ruby. In the ruby tracker Matz himself states this is a compromise. So now Ruby is getting half-baked compromises that look out of place, all to appease some people making requests.<p>If the requested functionality is so pertinent, then a <i>proper</i> solution should be made, in line with Ruby&#x27;s style. Not cryptic sigil soup with @ and .:, etc.<p>If a feature exists, it will get abused down the line. I do not want to read Ruby codebases that have @1, @2, @3, etc instead of named variables. We all know that temporary code is permanent. Just making this syntax possible is terrible.<p>I have to say I&#x27;m disappointed. I have enjoyed using Ruby for the last ~5 years but I disagree strongly with this syntax change.