---
title: "Discussion on \"Jiff 1.0 vs chrono and time: Parsing, Formatting and Time Zone Conversion, Measured\" | Hashnode"
description: "Discussion on \"Jiff 1.0 vs chrono and time: Parsing, Formatting and Time Zone Conversion, Measured\". I started a small Rust service last week, nothing fancy, and hit the decision every Rust project hits sooner or later: which datetime crate do I reach for? Chrono has been the default answer for years"
url: "https://hashnode.com/posts/jiff-1-0-vs-chrono-and-time-parsing-formatting-and-time-zone-conversion-measured/6afba9d3781a0fffedb4da0a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Jiff 1.0 vs chrono and time: Parsing, Formatting and Time Zone Conversion, Measured](https://aheadkit.hashnode.dev/jiff-1-0-vs-chrono-and-time-parsing-formatting-and-time-zone-conversion-measured?utm_source=hashnode&utm_medium=feed)

I started a small Rust service last week, nothing fancy, and hit the decision every Rust project hits sooner or later: which datetime crate do I reach for? Chrono has been the default answer for years

1d ago · 9 min read · aheadkit.hashnode.dev  
Read the article

-   [#rust](https://hashnode.com/tag/rust)
-   [#datetime](https://hashnode.com/tag/datetime)
-   [#benchmarking](https://hashnode.com/tag/benchmarking)
-   [#programming-ciovqvfcb008mb253jrczo9ye](https://hashnode.com/tag/programming-ciovqvfcb008mb253jrczo9ye)

## Written by

[Abdus Salam](https://hashnode.com/@aheadkit)

@aheadkit

  
[View profile](https://hashnode.com/@aheadkit)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
