RE: [PEAR-DEV] The point (BC breakage)

> -----Original Message----- > From: Joshua Eichorn [mailto:jeichorn@joshuaeichorn.com] > Sent: Friday, September 26, 2003 12:42 PM > To: Pierre-Alain Joye > Cc: Greg Beaver; pear-dev@lists.php.net > Subject: Re: [PEAR-DEV] The point (BC breakage) > > > Pierre-Alain Joye wrote: > <snip> > > > > >The maximum crap I can see: > > > >pear list > >Foo_v1 > >Foo_v2 > >Foo_v3 > >Foo_v4 > > > >where 30 other packages done by the user depend on every single Foo. > >Does that make it work on them? not really, the 2 years old release is > >still installed and heh, he still does not have the time to upgrade > >his old code (or do not like to work on 2 years old codes). > > > > > I thought this was the point, 2 years latter you can still use the old > version if you want to, PEAR shouldn't be forcing people with working > code to upgrade, i have lots of php code that i don't do anything but > security upgrades on until im doing feature work. I just don't have > time to upgrade my tens of thousands of lines of php code at the same > time, no matter how nice the features on the new version are. > > -josh > > >pierre > > > > > > Thank you Josh, you are 110% correct. Think Y2K crisis. Code running on mainframes that was 40 years old, 30 years old, 20 years old, 10 years old, 1 year old, 10 days old that all depended on different versions of the same library. To the point that it was easier to start over with current technology than to fix the problem in a lot of cases. You don't intentionally F*** the code just because you don't think that someone should not be running 20 or 30 year old code. Not if you acutally want someone using your code. Maybe you don't want anyone using PEAR? Thanks, Rob