#JodaTime
48 hours ≠ 48 hours.

DST doesn’t crash Java systems — it quietly corrupts them.

A hands-on Quarkus story about Joda-Time, billing bugs, and how to migrate safely to java.time without breaking production.

buff.ly/o5fVR2B

#Java #Quarkus #DST #JodaTime #EnterpriseDev
January 31, 2026 at 7:15 AM
This exchange between @dylanbeatt.ie and @jonskeet.uk makes me wonder, given that Nodatime is presumably based on Jodatime - what is there in the .NET ecosystem that #java folks could steal? (Exempting #LINQ for the usual well-known reasons).
The single most egregious fuckup in the history of computering is the thing where a person in Edinburgh uses a website hosted in Frankfurt to specify the start time of an event in Seattle and the web server believes even for a fraction of a second that it is remotely capable of not ballsing this up.
May 21, 2026 at 11:18 AM
Java's evolution gives us more choices - use external libraries or embrace language features? As with Java 8's date-time API replacing JodaTime, we should regularly reassess these decisions. Document why you chose a dependency so future developers can revisit when the ecosystem evolves. #Java
May 3, 2025 at 7:22 PM
That’s what I meant. Java got Jodatime library, then a new core library. JavaScript got MomentJs library, then a new core library Temporal (very recently). .Net got DateOnly and TimeOnly, but they feel like band-aids, not fixes.
May 21, 2026 at 4:14 AM
[ANN] Hodatime - Batteries included Date/time library
Hodatime is a date and time library for Haskell, inspired by Noda Time (itself, inspired by Joda Time) and Erik Naggum’s “The Long, Painful History of Time”. This library is intended to be batteries included, which is in contrast to most of the existing Haskell date time work (elegant as they are). It continues the work of Jodatime and Nodatime, distinguishing between civil and physical time but, just as Nodatime tightened the type safety of Jodatime, Hodatime excludes even more incorrect code due to Haskell’s type system. Highlights: * Multiple calendars — Gregorian, ISO, Julian, Coptic, Persian (astronomical Solar Hijri), Islamic (parameterised over the leap-year rule), and Hebrew — with lossless conversion between them. * Time zones read from the operating system (the IANA/Olson database on Unix, the registry on Windows), with explicit handling of skipped/ambiguous local times. * A composable pattern system where one field definition yields both a parser and a formatter, so the two can’t drift apart. * Locale-aware formatting driven by the host’s own locale data. Internally an instant is counted from 1 March 2000, not the Unix epoch. The reasons, as discussed in Naggum’s work are: starting the year in March pushes February — and its awkward leap day — to the end of the year, so the leap day never shifts the offsets of any other month and the date arithmetic stays uniform. And anchoring at 2000, a leap year that begins a fresh 400-year Gregorian cycle, makes the internal cycle/century/day-in-century breakdown fall out cleanly. Each calendar is free to use whatever epoch is most natural for its own math; the shift onto the shared timeline happens only at the boundary. It’s BSD-3-licensed, builds across GHC 9.4–9.10 on Linux/macOS/Windows, and has quietly been in development for years — 1.0 is the first release I’ve actually announced. Feedback very welcome.
discourse.haskell.org
July 31, 2026 at 5:56 AM
Interesting. I was looking at Jodatime, but it seems that Java has surpassed Jodatime in terms of features and usability: stackoverflow.com/a/24635657/3...
Differences between Java 8 Date Time API (java.time) and Joda-Time
I know there are questions relating to java.util.Date and Joda-Time. But after some digging, I couldn't find a thread about the differences between the java.time API (new in Java 8, defined by JSR ...
stackoverflow.com
February 11, 2025 at 11:08 AM
Case in point: date/time. NodaTime has been around for ages, and while JodaTime became that accepted standard ad JSR 310 was a way to co-opt it with minimal effort, .NET developers are largely holding onto their DateTime.UtcNow.
November 29, 2025 at 7:13 AM