3 ms·
I haven't spent a lot of time with Java, but you can generally compile old java source with new compilers as well as run old java bytecode with new runtimes. Ol
by toast0 6y ago
I haven't spent a lot of time with Java, but you can generally compile old java source with new compilers as well as run old java bytecode with new runtimes. Old and new code can interact with reasonable limits. You may be limited by the available runtime depending on where you need to run code, of course.
The same is true for Erlang/BEAM/OTP. You can even dist connect old and new VMs as long as you're careful not to send things the old VM won't understand (like Maps to a BEAM from before Maps). Erlang does tend to actually remove deprecated things after a few releases, unlike Java though, so it can be difficult to support more than two or three releases.
In both Java and Erlang, you can upgrade before your dependencies, at least most of the time, but that doesn't seem to be the case for python 2 -> 3, which means people are stuck on 2 when they want to use 3, until their dependencies update or they take over or abandon them. That's not a quick process which is why people are still upset.