5 ms·
Java 8, as in from 2014?
by webprofusion 2y ago
Java 8, as in from 2014?
- creshal 2y agoJava 8, as in "extended support until 2030 because too many companies would rather pay for that than upgrade"
- yardstick 2y agoHonestly it just shows how poorly executed the changes were in 9, 11, 17 that made it so difficult for companies to migrate.
- markus92 2y agoThe javax stuff really got us.
- alyandon 2y agoIndeed and I wish more people really understood this. I don't really like to target JDK8 as a supported version at work. However, I have to because of large, complex dependencies (some third-party with no source available) that have no drop-in replacements that will work under JDK9 and beyond. Finding replacements for dependencies (or rewriting them), testing, etc to move to newer versions of Java is a cost the business is not willing to absorb at this point. I expect that eventually when JDK8 has no viable support options and the cost of maintenance becomes too great the business will decide to jettison the whole stack and replace it with something else that likely won't be Java based.
- zelos 2y agoScaled from Java years to JS frontend years, that's like late 2022.
- robertlagrant 2y agoCertainly from a build system perspective.