> People try to run JVM versions across 10 years and face "small" issues with builtins. GP's point was mainly about missing interfaces, missing methods, typos etc.
Indeed -- well put.
> Java is “statically typed” amd has the same issues during runtime with different JVM versions.
Nothing is ever perfect -- there can be some occational runtime incompatibilities when very old Java code is run on new VMs.
But the effort in moving between one Java version and another Java version that came out many years later is likely order of magnitudes less than if you did the same thing in Ruby. There is simply no comparison.
Indeed -- well put.
> Java is “statically typed” amd has the same issues during runtime with different JVM versions.
Nothing is ever perfect -- there can be some occational runtime incompatibilities when very old Java code is run on new VMs.
But the effort in moving between one Java version and another Java version that came out many years later is likely order of magnitudes less than if you did the same thing in Ruby. There is simply no comparison.