Earlier quoted context omitted.
i do not see problems with axum. we wrote some macro(with muncher) which allows strongly typed and yet dry per method error, error split of public part vs internal log only(with backtrace crate trace capture), full openapi support(via schemars) and we do not use anyhow. whole article is rot and bad advice.
mind sharing a link?
https://zo-devnet.n1.xyz/docs#tag/default/post/action - mixes binary encoding, headers, and numeric errors embeeding (http goes to binary tx format).
all strongly typed without duplicated boilerplate.
inside - ad hoc error assembly - display_doc,derive_more, backtrace - no anyhow, not thiserror, no snafu.
fail fast and panic a lot, covered by proptests(toward fuzzytests).
used https://github.com/target-san/scoped-panic-hook to catch panics as exceptions.
was thinking to use https://github.com/iex-rs/lithium
panics = bugs or undefinenide behavour.