7 engineers on Hacker News describe using serde first-hand: 6 endorse it, 1 regret it, 0 are mixed.
“I have been using serde without issues, and never resorted to `serde::Value`, the untyped option, so far.”
endorse · personal · tcfhgj · 2026-11-05 · source ↗ · wrong label?“thanks to serde it's easy to switch between different serialization formats.”
endorse · personal · rekireki · 2025-12-28 · source ↗ · wrong label?“The moment I get something out of serde in Rust, I know for a fact this is a string.”
endorse · personal · kajaktum · 2022-11-28 · source ↗ · wrong label?“Serde is by far the biggest boon of the language.”
endorse · production · hresvelgr · 2021-12-21 · source ↗ · wrong label?“using serde feels like having superpowers.”
endorse · personal · paulgb · 2021-12-18 · source ↗ · wrong label?“We switched from serde to our own serialization / deserialization scheme (it still uses serde, but only for the JSON part)”
regret · production · idubrov · 2019-08-22 · source ↗ · wrong label?“every core "functionality" library (serde, uuid, rand, chrono, soon to be futures I hope, and innumerable more) is the best implementation”
endorse · personal · zanny · 2018-11-29 · source ↗ · wrong label?