Robert Klemme wrote in post #986190:
>> ...
>>
>> Just curious about possible removal of method aliases in a future ? I
>> know it would be very difficult decision to break backward
>> compatibility, but because these are synonyms/aliases it won't be too
>> hard to write conversion tool for existing sources.
>
> Why bother?  This generates superfluous efforts because you gain
> nothing other than some abstract "cleanness" or removal of redundancy.
>
>> Is there same intention to clean Ruby's core libraries ?
>> When'll be the time, Ruby would need no more to attract programmers from
>> different envirnoments and start with cleaning out ?
>
> I don't think there are any such intentions.  I'd strongly object to
> them if there were.  This just does not give any benefit and there
> would be far better candidates for cleaning up (class variables should
> be banned for example).
>
> Cheers
> ne
> robert

I'd guess reasons are obvious. You have to remember not only method
names but also their aliases you personally do not use just for the
sake of understanding other's source code. It does make you not a bit 
more
productive. I'd prefer to spare my memory for much more important and 
useful things.

If you'll have to analyze thousands of lines of code even with
inconsistent mix-up of both method aliases, your oppinion would
certainly change.

-- 
Posted via http://www.ruby-forum.com/.