Stop using DateTime in 2026 (unless you work for UNESCO)
DateTime has been considered deprecated in Ruby since 3.0. It’s 2026. Why are people still using it?
During a recent code review, we found this:
whatever.starts_at = DateTime.now
When asked why DateTime instead of Time, the response was: “DateTime handles a wider range of dates.”
That was partially true. In 2008. On 32-bit systems.
DateTime’s range advantage died in Ruby 1.9.2
Before Ruby 1.9.2 (released in 2010), Time was limited by the system’s time_t type — typically 32-bit signed integer covering 1901-2038. DateTime had a much wider range.
Ruby 1.9.2 changed this. Time started using a signed 63-bit integer representing…















![[8/4] How a Scotsman saved hours of my time by turning an LLM into my virtual assistant](https://digitalpress.fra1.cdn.digitaloceanspaces.com/xhtzjbw/2025/12/ChatGPT-Image-Dec-27--2025--05_51_01-AM.png)
![[8/4] How a Scotsman saved hours of my time by turning an LLM into my virtual assistant](https://digitalpress.fra1.cdn.digitaloceanspaces.com/xhtzjbw/2025/10/Screenshot-2025-10-26-at-10.25.22.png)
![[8/4] How a Scotsman saved hours of my time by turning an LLM into my virtual assistant](https://digitalpress.fra1.cdn.digitaloceanspaces.com/xhtzjbw/2025/10/Screenshot-2025-10-26-at-10.26.09.png)