Question 1

Should I use Cheshire or data.json for my Clojure project?

Accepted Answer

Cheshire is faster and supports more types like Date and UUID, but data.json is simpler and part of Clojure core. Choose Cheshire for performance and extended features, data.json for basic, dependency-light JSON handling.

Question 2

How to encode a Java Date with a custom format in Cheshire?

Accepted Answer

Use the :date-format option in generate-string, e.g., (generate-string {:date (java.util.Date.)} {:date-format "yyyy-MM-dd"}). This allows flexible date representation without post-processing.

Question 3

Does Cheshire support lazy parsing of large JSON files?

Accepted Answer

Yes, Cheshire offers parsed-seq for lazy decoding from streams, enabling memory-efficient handling of large JSON datasets without loading everything at once.

Question 4

What is SMILE format and when should I use it with Cheshire?

Accepted Answer

SMILE is a binary JSON format for compact data exchange. Use Cheshire's generate-smile and parse-smile functions when network bandwidth or storage efficiency is a priority over human readability.

Question 5

How do custom encoders affect performance in Cheshire?

Accepted Answer

Custom encoders use a slower path than the default encoder, as noted in the README. They add flexibility but can impact speed for encoding custom classes in performance-sensitive applications.

Question 6

Is Cheshire compatible with Babashka for scripting?

Accepted Answer

Yes, Cheshire is built into Babashka, making it a seamless choice for Clojure scripting tasks that require fast JSON encoding and decoding without additional dependencies.

Cheshire

What is Cheshire?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions