News for hackers. Stuff that matters.
Re:All about java.util.Date by shouldbworking on Sunday April 23, 2017 @04:48PM (#14180361)
TLDR: It sucks balls use Jodatime

Edit: I was wrong my bad

Re:All about java.util.Date by pavel_lishin on Sunday April 23, 2017 @04:54PM (#14180390)
> Note that from Java SE 8 onwards, users are asked to migrate to java.time (JSR-310) - a core part of the JDK which replaces this project.

http://www.joda.org/joda-time/

Re:All about java.util.Date by alkonaut on Monday April 24, 2017 @05:43AM (#14182998)
So basically a joda-like sane api was included as a JSR, making joda obsolete?

Are there any such plans for .NET and NodaTime? They have a more "everything is a package"-philosophy these days, but sensible dates and times really ought to be right in the corlib, especially since the bad dates and time apis are already there.

Re:All about java.util.Date by jonskeet on Monday April 24, 2017 @12:38PM (#14185698)
I've mentioned a few times to MS folks that I'd be very happy for the mscorlib team to make Noda Time redundant. They haven't bitten yet though.
Re:All about java.util.Date by trumpeta on Sunday April 23, 2017 @04:52PM (#14180383)
I have been using the Java 8 Time API which seems to have been based on Jodatime, and one dependency less
Re:All about java.util.Date by masklinn on Sunday April 23, 2017 @05:01PM (#14180421)
> Java 8 Time API which seems to have been based on Jodatime

JSR-310 was developed in large parts by the author of Joda, more than based on Joda it's also based on lessons learned from Joda.

Re:All about java.util.Date by Insanity on Sunday April 23, 2017 @04:54PM (#14180389)
Only if you are using a version before Java 8
Re:All about java.util.Date by jsymolon on Monday April 24, 2017 @08:11AM (#14183583)
Represent !

Some of the back end systems are still on 1.2.

Something about "no money for licenses and upgrades" on items that use Java.

Not too many in-house developers, aka zero, want to touch that core system.