|
I have a theory <grin>. The trend in software development is getting away from regression testing and backwards compatibility. The current feeling is "if it passes my JUnit test, then it must be good". This basic tenet of the new programming model is the one that frightens me the most: because your JUnit test may not take into account what people are doing in the field, passing the JUnit test does NOT ensure backwards compatibility. And since another tenet of this programming philosophy is to program via refactoring rather than design (that is, just get it to work and rewrite it later), breaking backwards compatibility is becoming more the rule rather than the exception. Combine this with the fact that for the last couple of years just about every "standard" for Java has been more of a suggestion than a standard, meaning that every programmer can reinterpret the meaning and "refactor" the code, and it's clear that we're in for more of this rather than less. Joe > From: Nathan M. Andelin > > > He suggested that I go back even further with my JVM > > than 1.4.1_04 ... which I can't do because of other > > applications. > > I haven't kept up with JVM issues, but why wouldn't newer JVM versions > support fairly recently deployed applets?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.