On Tuesday, August 9, 2011 4:46:53 PM UTC-4, Casper Bang wrote: > It's interesting that SQLDeveloper always does version checking and > warns users of potential problems, it kind of says something about the > developers lack of trust in binary backwards compatibility of the Java >
No, this only says something about the developer's lack of confidence about their own code's portability/compatibility. We're not in the JDK 1.2->1.3 times anymore; backwards compatibility of new Java versions has been exceptionally good as a rule, for a longtime. Of course not perfect, some regressions happen, but I'd say that java's current track record is the best of any major platform - your favorite desktop or mobile operating system, browser, desktop environment, Flash player etc., typically breaks more applications at each major release than any recent major release of Java. At least that's my experience as an early adopter. There are tons of software much bigger than SQLDeveloper that routinely transition to major JDK updates without a hitch. The real problem, most likely, is that SQLDeveloper is not a pure-Java app, they have a bunch of DLLs - not just launcher stuff but things like idenative.dll and jdevnative.dll. In the Oracle forum, they suggested to copy JDK 7's bundled msvcr100.dll to improve compatibility with JDK 7. I've tried that, no improvement at all; but that recommendation is a huge smoking gun. The problem is that they have some crappy native dependencies that they inherit from JDeveloper frameworks. A+ Osvaldo -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/BLqdcAMDOkIJ. 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.
