# joda Published articles for joda. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior DevFeed: [Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2021-09-25T00:55:00Z Content type: opinion Language: en Sources: [Stephen Colebourne]() Topics: [DateTime](), [Programming](), [systems](), [Operating system]() Tags: [blog](), [jdk](), [joda](), [operating-systems](), [smartphones](), [systems](), [timezone]() ### AI overview The article criticizes a proposed change to the IANA timezone database that would make Europe/Oslo an alias of Europe/Berlin because their post-1970 data matches. It argues that this could replace researched pre-1970 Oslo data with Berlin data and cause Joda-Time tests and timezone identifier handling to fail. ### Source excerpt The last time I wrote about the timezone database on this blog, the database was under threat from a lawsuit. Fortunately that lawsuit went away relatively quickly as the company involved got the message that their action was a big mistake. Unfortunately this time the mess is internal. Paul Eggert is the project lead of the timezone database hosted at IANA, a position referred to as the TZ Coordinator. He is an expert in the field, having been involved in documenting timezone data for decades. Unfortunately, he is currently ignoring all objections to an action only he seems intent on making to solve an invented problem that only he sees as important. The database is the world's principle source of timezone information. The data is included in everything from operating systems to smartphones to programming language development kits such as the JDK. While you may never have heard of it, the sheer pervasiveness of the data makes the potential impact of change or damage pretty huge. The timezone database contains information about how clocks have varies in each region around the world. The mandate of the project is to record this information from 1970 onwards. Of course, computers being what they are, a function that returns the timezone for a given date can be passed in a pre-1970 date as well as a post-1970 one. For this, and reasons of completeness, the timezone database contains pre-1970 data as well as post-1970 data. If you go to your JDK or operating system and ask for the timezone offset for 1920-01-01 for the ID "Europe/Oslo" or "Europe/Berlin" you will get an answer: DateTimeZone oslo = DateTimeZone.forID("Europe/Oslo"); System.out.println(oslo.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 3600000 DateTimeZone berlin = DateTimeZone.forID("Europe/Berlin"); System.out.println(berlin.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 7200000 The proposed change is to downgrade "Europe/Oslo" to be merely an alias for "Europe/Berlin". The rationale is th ## Modern DateTimes on Android DevFeed: [Modern DateTimes on Android]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2019-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Artur Dryomov]() Topics: [Android](), [Java]() Tags: [android](), [java](), [joda](), [threeten](), [time]() ### AI overview This article explains the Java 8 date and time API on Android, including the use of ThreeTenBP and ThreeTenABP while native support remains limited. It recommends migrating from Joda-Time to ThreeTen-based APIs and describes separate dependencies for applications and JVM-based unit tests. ### Source excerpt Java 8 gave us a great gift -- the java.time package, known as JSR 310 and ThreeTen. The story behind java.time is unique. It was introduced in JEP 150 by an independent developer -- Stephen Colebourne (@jodastephen). Yep, the same person who designed and developed Joda-Time. It was even endorsed by Brian Goetz, the Java Concurrency in Practice author! The result is a great API -- explicit and direct, based on years of Joda-Time experience. ## Commercial support for Joda and ThreeTen projects DevFeed: [Commercial support for Joda and ThreeTen projects]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2019-01-09T12:23:00Z Content type: opinion Language: en Sources: [Stephen Colebourne]() Topics: [Java](), [Maintainers](), [Open Source](), [Security]() Tags: [java](), [joda](), [maintainers](), [open-source](), [security](), [threeten]() ### AI overview The article announces commercial support through Tidelift subscriptions for Joda-Time, Joda-Money, Joda-Beans, Joda-Convert, Joda-Collect, ThreeTen-Extra, and ThreeTen-backport. It explains that Tidelift directs part of subscription income to maintainers while leaving projects free and permissively licensed. ### Source excerpt The Java ecosystem is made up of many individuals, organisations and companies producing many different libraries. Some of the largest projects have long had support options where users of the project, typically corporates, can pay for an enhanced warranty, guaranteed approach to bug fixes and more. Small projects, run by a single individual or a team, have been unable to offer this service, even if they wanted to. In addition, there is a more subtle problem. The amount a small project could charge is too low for a corporate to pay. This sounds odd, but was brought home to me by this thread on twitter: As the thread indicates, it is basically impossible for a corporate to gift money to a small project, and it is not viable for small projects to meaningfully offer a support contract. The problem is that not paying the maintainers has negative consequences. Take the recent case where a developer handed his open source project on to another person, who then used it to steal bitcoins. Pay the maintainers I believe there is now a solution to the problem. Tidelift. Tidelift offers companies a monthly subscription to support their open source usage. And they pay some of that income directly to the maintainers of the projects that the company uses. Maintainers are expected to continue maintaining the project, follow a responsible disclosure process for security issues and check their licensing. Tidelift does not get to control the project roadmap, and maintainers do not have to provide an active helpdesk or consulting. See here for more details. As such, I'm now offering commercial support for Joda-Time, Joda-Money, Joda-Beans, Joda-Convert, Joda-Collect, ThreeTen-Extra, ThreeTen-backport via the Tidelift subscription. This is an extra option for those that want to support the maintainers of open source but haven't been able to find a way to do so until now. The Joda and ThreeTen projects will always be free and available under a permissive licence, so there is no need to w ## A propos de Joda-Time DevFeed: [A propos de Joda-Time]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2010-02-09T17:32:06Z Content type: tutorial Language: fr Sources: [The Coffee Workshop]() Topics: [Java](), [API](), [DateTime]() Tags: [api](), [bug](), [java](), [jdk](), [joda](), [thread](), [time](), [timezone]() ### AI overview This French developer article discusses the limitations of Java's legacy date and time API, including thread-safety, performance, and implementation issues. It introduces Joda-Time as a more consistent and usable alternative, explains its relationship to JSR-310, and demonstrates concepts such as immutable DateTime objects, instants, and time zones. ### Source excerpt Je suis un peu surpris de voir que beaucoup de développeurs utilisent encore énormément l'API temps du JDK. C'est la raison pour laquelle j'ajoute une nouvelle entrée sur le web à ce sujet.