• Sources: post, HN discussion
  • Summary: The post motivates Deser with three worked failures it attributes to Serde's design rather than to bugs: an internally tagged enum breaking when any crate in the graph turns on serde_json's arbitrary_precision, flatten turning integer map keys back into strings, and deserialize_with that cannot be applied inside an Option. The stated costs are that Deser drops non-self-describing formats such as protobuf by design, reads about 10 percent slower than serde_json on average for JSON, produces worse binary bloat, and uses unsafe internally.
  • Why it matters: The three failures are properties of Serde as shipped, so they are worth checking against an existing codebase whether or not Deser is adopted.