Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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 to be constantly updated because of the files that it includes. And that is a disadvantage. Maybe I am wrong.
Could you provide some clarity on the subject?
I’ve had almost entirely positive experiences with Joda Time. My one problem was when trying to construct my own time zone (for legitimate reasons, I assure you 🙂 I got some very weird exceptions, and the documentation wasn’t very good for that particular use case.
However, for the most part it’s been a joy to use – immutability makes code a lot easier to reason about, and thread-safety for formatters is hugely useful.
Yes, there are files to keep up to date – but at least you can keep them up to date. It’s not like they contain things which were unnecessary with Java’s built-in stuff, it’s just that with Java’s mechanism you just couldn’t keep information like timezones up to date without significant hackery!
Basically, +1 for using Joda Time. The Java date/time API is one of the worst bits of the Java platform, IMO.