为非技术决策者（在客户端）升级到Java 6的原因和优势 [英] Reasons and advantages for upgrading to Java 6 for a non-technical decider (at the client)
问题描述
我想从Java 5升级到Java 6.
我们都知道技术优势和好处，但是：
我有主要客户拒绝从java 5升级到java 6的问题，因为风险和我们没有/太少的好处（银行业）。
客户可以回答非技术性决策者从升级中得到什么好处 - 或者如果他将继续使用java 5会出现哪些问题/后果？
这不是一个火与忘记的产品，它通过新的功能/特性进行了激活扩展 - 开发一直并且将会不断发展 - 开发团队肯定会从jdk 6功能/工具中获益。 / p>
编辑： Java 5的 EOL 确实是一个有效点，但它没有说服客户，因为他正在使用 IBM JRE / JDK 5 ，这似乎未达到目的o生活尚未。而且，除此之外，客户说：
Java 5运行良好多年，不太可能出现新的，看不见的问题
随着时间的推移，客户端将越来越需要升级，因为以下内容：
- 某些新版本不支持Java 5硬件或操作系统平台，
- 相对于较新的Java版本，性能较差，
- 相对于较新的Java版本，编码和测试成本较高;例如由于旧API的笨拙，无法使用流等，
- 增加供应商支持成本 1 ：您必须支付for support 获取安全补丁，而且版本越旧，你支付的越多（我认为）
- 难以让Java开发人员继续使用Java 5项目，
- 不再为Java 5开发和支持第三方Java库，
- 合规性问题;例如 https://stackoverflow.com/a/3434063/139985
- 等等on。
但是客户端延迟升级的时间越长，涉及的Java版本就越大，并且工作量越多（并且可能会带来痛苦）将参与。
客户延迟的时间越长，硬件配置，开发商成本，延期项目等的累计成本就越大。
为了说明，假设您已等待10年才能从Java 1.1升级到Java 1.2。这意味着您将花费额外的10年时间开发使用 Hashtable 和 Vector 作为其主要数据结构的应用程序。当你最终升级时，你将拥有10年的额外遗留代码，这些代码比使用Java 1.2集合编写时更难维护。
但是最重要的是，如果客户坚持要保留旧版本的Java，您需要遵循他们的意愿（并确保您转嫁额外费用！），或找到退出合同关系的方法客户。
1 - 生命周期终止/服务终止日期因供应商而异但AFAIK所有主要供应商现在已经使用EOL'd Java 5。事实上，Oracle也有EOL的Java 6和Java 7。
I'd like to upgrade from Java 5 to Java 6. We all know about the technical advantages and benefits, but:
I have the problem that a major client refuses to upgrade from java 5 to java 6 because of "the risks" and "no/too few benefits for us" (banking sector).
What can be answered to a non-technical decider at the client what benefits he'll get from an upgrade - or otherwise which problems/consequences may arise if he'll stay with java 5?
It's not a "fire and forget"-product, it's activly extended with new functionality/features - the development is and will be constantly going on - the dev team would definitly benefit from the jdk 6 features/tools.
EDIT: The reached EOL of Java 5 is a valid point indeed, but it doesn't convince the client because he is using the IBM JRE/JDK 5, which seems that it has not reached its end of life yet. And, beside that the client stated: "Java 5 is running fine for years and its unlikely that new, unseen problems arise"
Over time, the client will increasingly need to upgrade because of things like:
- Java 5 not being supported on some new hardware or operating system platform,
- poor performance relative to newer Java releases,
- greater coding and testing costs relative to newer Java releases; e.g. due to the "clunkiness" of older APIs, not being able to use streams, etc
- increasing cost of vendor support1: you have to pay for support to get security patches, and the older the release the more you pay (I think)
- difficulty of retaining Java developers to work on Java 5 projects,
- third party Java libraries no longer being developed and supported for Java 5,
- compliance issues; e.g. https://stackoverflow.com/a/3434063/139985
- and so on.
But the longer the client delays upgrading, the larger the Java version jump involved, and more work (and potentially pain) that will be involved.
And the longer the client delays, the larger the accumulated costs of things like hardware provisioning, developer costs, deferred projects and so on.
To illustrate, suppose that you had waited 10 years to upgrade from Java 1.1 to Java 1.2. That would mean that you would have spent extra 10 years developing applications that used Hashtable and Vector as their primary data structures. And when you finally upgraded you would have 10 years worth of additional "legacy" code that is more difficult to maintain than if it had been written using Java 1.2 collections.
But the bottom line is that if the client insists on staying an old version of Java, you need to either go along with their wishes (and make sure that you pass on the extra costs!), or find a way to exit your contractual relationships with the client.
1 - The End of Life / End of Service dates vary from one vendor to the next, but AFAIK all major vendors have EOL'd Java 5 by now. Indeed Oracle have EOL's Java 6 and Java 7 as well.
这篇关于为非技术决策者（在客户端）升级到Java 6的原因和优势的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
