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

Evaluating using Boost.JSON #1107

Open
jcoupey opened this issue Apr 29, 2024 · 1 comment
Open

Evaluating using Boost.JSON #1107

jcoupey opened this issue Apr 29, 2024 · 1 comment

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Apr 29, 2024

Boost has its own JSON library, and I've heard that it's easier and more intuitive to use than rapidjson. Switching may not harm performance, provided we trust their benchmarks.

Add to this the fact that rapidjson is painfully unmaintained unversioned, maybe we should consider switching. Of course we'd have to evaluate that in the light of our use-case. The most demanding part for us is probably the parsing of huge matrices spitted out by routing engines.

@SebMilardo
Copy link
Contributor

Hi! Could you assign this issue to me?

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

No branches or pull requests

2 participants