ARTS002 - 翻译 《Java Concurrency in Practice》Preface 序

定期发布一篇英文原文翻译，希望可以坚持下来！

《Java Concurrency in Practice》Preface 序

• 【生词】

英文	中文
preface	序
midrange	中端
not coincidentally	非偶然的
maintainers	维护人员
patch	修补、打补丁
former	前任
painful	痛苦的
ultimately	最终
reveal	揭示
rife	普遍的
manifest	显示、显现
mismatch	匹配不当
mechanism	机械装置、机件、方法、机制
nevertheless	然而、尽管如此
excessively	过分地
novice	初学者、新手
facility	设备、工具
underlying	根本的、潜在的
scenario	方案、预想、场景
motivate	成为…的动机、是…的原因
inclusion	包括
mental model	思维模式
performant	性能优化

• 【标题】

Preface
序

• 【原文/翻译】

At this writing, multi‐core processors are just now becoming inexpensive enough for midrange desktop systems.
当在写这篇的时候，多核处理器对于中端桌面系统已经便宜。

Not coincidentally, many development teams are noticing more and more threading‐related bug reports in their projects.
非偶然的，很多开发团队在他们的项目里正注意到越来越多跟线程相关的问题报告。

In a recent post on the NetBeans developer site, one of the core maintainers observed that a single class had been patched over 14 times to fix threading‐related problems.
在netbeans开发者网站近期的一篇帖子上提到，一位核心维护人员注意，一个简单的类为了解决线程相关问题被修补超过14次。

Dion Almaer, former editor of TheServerSide, recently blogged
(after a painful debugging session that ultimately revealed a threading bug) that most Java programs are so rife with concurrency bugs that they work only “by accident”.
TheServerSide的一位前任编辑Dion Almaer，近期发表博客说道(在一个痛苦的调试会议之后，最后揭露了一个线程问题），大多数Java程序都普遍的有并发问题，以至于它们只能 “偶然” 地工作。

Indeed, developing, testing and debugging multithreaded programs can be extremely difficult because concurrency bugs do not manifest themselves predictably.
实际上，开发，测试，调试多线程程序十分的困难，因为并发问题是不可预测的。

And when they do surface, it is often at the worst possible time in production,under heavy load.
当问题出现时，通常是在生产中最糟糕的时候，在并发压力大的时候。

One of the challenges of developing concurrent programs in Java is the mismatch between the concurrency features offered by the platform and how developers need to think about concurrency in their programs.
用Java开发并发程序的挑战之一是平台提供的并发特性与开发人员需要考虑他们程序的并发性，两者之间的不匹配问题。

The language provides low‐level mechanisms such as synchronization and condition waits, but these mechanisms must be used consistently to implement application‐level protocols or policies.
该语言提供了低级机制，如同步和条件等待，但这些机制必须一致地用于实现应用级别协议或策略。

Without such policies, it is all too easy to create programs that compile and appear to work but are nevertheless broken.
如果没有这样的策略，创建程序可以编译和运行，但程序仍然非常容易被破坏。

Many otherwise excellent books on concurrency fall short of their goal by focusing excessively on low‐level mechanisms and APIs rather than design‐level policies and patterns.
许多其他关于并发的优秀书籍都没有达到目标，因为他们过度关注低级机制和api，而不是设计级别的策略和模式。

Java 5.0 is a huge step forward for the development of concurrent applications in Java, providing new higher‐level components and additional low‐level mechanisms that make it easier for novices and experts alike to build concurrent applications.
Java 5.0是Java中并发应用程序开发的一大进步，它提供了新的高级组件和其他低级机制，使得初学者和专家更容易构建并发应用程序。

The authors are the primary members of the JCP Expert Group that created these facilities; in addition to describing their behavior and features, we present the underlying design patterns and anticipated usage scenarios that motivated their inclusion in the platform libraries.
这些作者是JCP专家组的主要成员，创造出这些工具，除了描述它们的行为和特征，我们还展示了潜在的设计模式和预期的使用场景，促使它们被纳入平台库。

Our goal is to give readers a set of design rules and mental models that make it easier and more fun to build correct,performant concurrent classes and applications in Java.
我们的目标是为读者提供一套设计规则和思维模式，使在Java中构建正确、高性能的并发类和应用程序变得更加容易和有趣。

We hope you enjoy Java Concurrency in Practice.
我们希望你们能享受这个书。

Brian Goetz
Williston, VT
March 2006