True but is the payback worth the trouble? The only way to truly know your app can run is to test each and every scenario of it, very hard to do, so its safest to just stay with an old. A base class might have gotten a new method, a bug which you relied on has been fixed etc.
So I kinda agrees with Matthew. Perhaps it's not worth it sacrificing innovation for (various levels of) backwards compatibility when it's often more a theoretical advantage than a realistic, practical one. /Casper On Oct 1, 12:35 pm, "Lars Westergren" <[EMAIL PROTECTED]> wrote: > > So the funny thing to me, is that unless i'm missing something, all the > > effort that Sun went to trying to keep backwards compatibility was all for > > nowt, as there's plenty of other factors that bind applications to pre-1.5, > > that can't be resolved trivially. > > Logical fallacy I think. Isn't this like saying "Efforts to reduce > crime are for nowt because there is still crime"? Every time you start > a java app on a new JVM and it works, that is one success. > > Cheers, > Lars --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
