Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison with devalue #50

Open
aleclarson opened this issue Jan 13, 2025 · 1 comment
Open

Comparison with devalue #50

aleclarson opened this issue Jan 13, 2025 · 1 comment

Comments

@aleclarson
Copy link

Hi, could you explain the differences between this and devalue? Thanks

@lxsmnsyc
Copy link
Owner

There's a lot of serializer libraries so I didn't document any comparison to any but to answer your question, it all comes down to performance and features.

Seroval offers a lot more features when it comes to serializable values and modes (streaming and async), whereas devalue doesn't do this out-of-the-box. See https://github.com/lxsmnsyc/seroval/blob/main/docs/serialization.md and https://github.com/lxsmnsyc/seroval/blob/main/docs/compatibility.md

Perf-wise, seroval runs, at most, twice as fast as devalue, you can check the benchmarks here: https://github.com/lxsmnsyc/seroval/blob/main/benchmark/results/csv/simple-object%20to%20string.csv

There's a lot more to flesh out, but I just described the more obvious ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants