> Except it's arguably necessary for backwards compatibility. An alter where too much stuff is sacrificed.
> The code is always shared in Java as there's only one copy of it. Well yeah the single non-parameterized type, but without knowledge of the parameterized superset, the JIT's optimization options are limited. > If you have a valuable community who uses the word 'enterprise' as a > positive thing, you don't want to be invalidating their old code. Please, "enterprise" customers run their stuff on old runtimes anyway, as it's the only way to truly ensure compatibility. Even the smallest change no test-kit can guard against (i.e. default localization pattern changing from Java 1.5 to 1.6) can cause havoc. -- 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.
