#deser#serialization#rethinking#rust#rust serialization#rethinking rust#rethinking rust serialization
7 comments
satvikpendem1 day ago
How does this compare to facet [0][1] by fasterthanlime? Seems some of the reasoning is similar especially for compile time bloat.
[0] https://facet.rs
[1] https://fasterthanli.me/articles/introducing-facet-reflectio...
nicoburns1 day ago
Facet set out to compile faster, but AFAIK it never actually achieved that goal.
duhhhhh12121 day ago
the_mitsuhikoabout 19 hours ago
I think this is a case of pangram's attribution being confused. All code examples are AI generated but it places the attribution on the text that surrounds it.
ramon1561 day ago
next time just write the post yourself. I don't need an entire paragraph to explain that deser = serde but reshuffled
qchris1 day ago
I'm not sure if this author used an LLM, but I think you've misunderstood that paragraph. At worst, the line you're referencing is a tongue-in-check little introduction into a paragraph that describes the top-level differences in approach to serialization that the two libraries take.
ydj1 day ago
deser might also just be deserialize shortened, and I was wondering if it was something focused on deserialization only. As such, I didn’t find a quick little note on the etymology to be a particularly egregious waste of words.
Read the full thread on Hacker News →
Related stories
- Deser: Rethinking Rust Serializationlucumr.pocoo.orgLobsters · 44 points · 1 day ago
- Lobsters · 13 points · over 2 years ago
- Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022opensource.googleblog.comLobsters · 81 points · over 3 years ago
- rust-glancer: An alternative LSP for Rust with focus on low memory usagerust-glancer.github.ioLobsters · 25 points · about 1 month ago
- Hacker News · 8 points · 3 days ago
- DEV Community · 0 points · 5 days ago