4 ms·
If that were so simple. What if your software gets deployed on an application server? If you upgrade, you need new support contract, this costs money plus leads
by piokoch 9y ago
If that were so simple. What if your software gets deployed on an application server? If you upgrade, you need new support contract, this costs money plus leads to possible deployment/config changes, for instance going from JBoss 5 EAP to JBoss 6 EAP is not a pleasant experience as almost all configuration was radically changed.
What if part of your application is audited and certified by some regulatory body, when you upgrade, you need to go through the process again.
Java value is stability, you can assume your software will run for 20 years without touching it.
- dragandj 9y agoNo one is forcing anyone to upgrade. What worked on Java 8 3 years ago, will work on Java 8 in 17 years. If your team have extra requirements (audit, certification etc.), it seems it sells enterprise software. All those things cost money, but I assume you also charge money. So, what's exactly the problem? It is a bit naive to expect to get ultra stability for free from your suppliers, but charge top dollar from your customers...
- coldtea 9y ago>No one is forcing anyone to upgrade. No, but they are restricting them from updating as easily as before -- unless they cough up dough.
- oblio 9y agoHow are they restricting the updates? I'm not sure I understand.
- coldtea 9y agoBy only providing fixes and security patches for a few months -- after that you need to move to the next version (with all that entails testing and adapting wise for large codebases), or you pay for enterprise support and get support for years. Before you could go to any version and expect it to be supported for years. Now, if you dare go to some version above 8, you're supposed to either pay (for long term support), jump directly to the next version after a few months, or stay without security fixes. (Or go OpenJDK and screw them).