<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zoneddatetime on Devops Monk</title><link>https://devops-monk.com/tags/zoneddatetime/</link><description>Recent content in Zoneddatetime on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/zoneddatetime/index.xml" rel="self" type="application/rss+xml"/><item><title>Date and Time API (JSR-310): LocalDate, ZonedDateTime, Duration, Period</title><link>https://devops-monk.com/tutorials/java8/date-time-api/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/java8/date-time-api/</guid><description>Why java.util.Date Had to Go java.util.Date was introduced in Java 1.0 and has been a source of bugs ever since:
Mutable — Date can be modified after creation, causing subtle bugs when passed between methods Not thread-safe — mutable state means shared dates need external synchronisation Poor API design — year is offset from 1900, months are 0-indexed, no time zone support on Date itself Deprecated methods — most of the useful methods on Date were deprecated in Java 1.</description></item></channel></rss>