From: Terry Poulin <bigboss64@...>
Date: 2007-09-05T07:09:06+09:00
Subject: Re: Ruby stupidities

John Joyce wrote:
> Indeed, at some point you simply have to break things to do new or
> better or different things. Endless backwards compatibility ends up
> with bloated, hacked up junk.
>
>

Change is good, as long as it is documented and changed for the better when it
breaks stuff.


Look at C, the changes can be quite extreme between old old code and new code.
But I think it was worth it. Then look at Windows, hell I think the C:\ thing
was stolen from 1960s OSes by DEC. Windows NT has to be compatible with users
minds and old versions software... Blast you can still run edit from an XP
machine.


Personally, as long as the changes are documented, fair warning is given
before breaking code written last week, and the updates to software come into
wide spread usage. I don't give a darn hehe.


Just my two cents.

TerryP.


--
    
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com