4 ms·
TLDR: It sucks balls use Jodatime Edit: I was wrong my bad
by shouldbworking 9y ago
TLDR: It sucks balls use Jodatime
Edit: I was wrong my bad
- trumpeta 9y agoI have been using the Java 8 Time API which seems to have been based on Jodatime, and one dependency less
- masklinn 9y ago> 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.
- Insanity 9y agoOnly if you are using a version before Java 8
- jsymolon 9y agoRepresent ! 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.
- pavel_lishin 9y ago> 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/ http://www.joda.org/joda-time/
- alkonaut 9y agoSo 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.
- jonskeet 9y agoI'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.
- deleted 9y ago[deleted]