Why Did Java's Infamous Date API Become Such a Historical Blunder?

The Notorious Java Date API: A Historical Blunder

The Java date API, known for its infamy, has been plagued by several flaws that have made it a notorious component of the Java SDK. These include its mutability, misrepresentation of date timestamps rather than dates themselves, and the lack of straightforward conversion between date components and the Date object. Additionally, the Calendar class is deemed clunky and attempts to merge multiple calendar systems into a single class.

Curiosity abounds as to how such glaring issues made their way into the Java SDK. Despite the apparent simplicity of these shortcomings, most notably the mutability of the Date class, it remains a mystery how these problems evaded detection.

According to sources, the renowned Java Programmers FAQ, version 07.X.1998, written by Peter van der Linden, addressed the issue succinctly:

"Class Date represents a specific instant in time, with millisecond precision. The design of this class is a very bad joke - a sobering example of how even good programmers screw up."

The author went on to criticize the Calendar class and its GregorianCalendar subclass, calling them "overengineered junk" licensed from Taligent.

The rationale behind the mutability of the early JDK classes, including Date, has been attributed to misguided optimizations. The intention was to encourage object reuse and avoid unnecessary copies, but this approach may have been misplaced with contemporary VMs.

Despite numerous shortcomings, the Java date API persists within the SDK, offering a sobering reminder of the potential pitfalls of API design and the inevitability of even the most experienced programmers making mistakes.

The above is the detailed content of Why Did Java's Infamous Date API Become Such a Historical Blunder?. For more information, please follow other related articles on the PHP Chinese website!