I want to convince the architecture manager to include the Joda-Time jar in our product.
Do you know any disadvantages in using it?
I think Joda-Time needs t
The choice of milliseconds for the underlying time continuum is good for implementing calendars of antiquity, and special calendars. Unlike many counters, the 64-bit millisecond counter has good range coverage for calendars of antiquity, with rollover properties in excess of +/- 260 million years.
It does not handle leap seconds. This is a good thing. A smooth transition is proposed by the atomic clock folks to allow systems that do not deploy leap seconds to incrementally adjust their clocks over 100 seconds to accommodate the leap second correction.
Maintenance of timezone tables will also be an issue.
The underlying continuum also allows an old French calendar and clock that divided a day into 10 intervals called metric time instead of 24 hours. The classic Chinese calendar divides a day into 100 increments, each just over 14 minutes in length. All of these calendars can be implemented and coordinated on the underlying millisecond time continuum.