-
Notifications
You must be signed in to change notification settings - Fork 55
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
Replace json11 with RapidJSON #3
Comments
Hi, There was only one reason for json11 library: a simple and convenient C++ API. Btw, that project was more alive at the time I've started to use it. Now it's really not improving. And true, its performance sucks comparing to RapidJSON and other highly optimized JSON libraries. |
For HTTPS support have you looked at the Requests C++ library: I found a good description of it here: |
rapidjson is a hot C++ json library at this moment. It's worth taking a look at |
I suggest using nlohmann/json instead. It's more modern, still maintained and pretty much as fast as rapidjson now. |
As I know, nlohmann is much slower: https://github.com/miloyip/nativejson-benchmark and it does not support stream writing (correct me if I’m wrong), which means that user has always create an intermediate DOM ( |
Have you seen boost.json? It seems that it has a good performance and also quite modern, |
Never used it myself nor have I seen it being used in other projects. Rapidjson/nlohmann feels like an industry standard at this point with the first used for more speed and the second for more convenience and readability. Oh, and there is also a json parser in boost.property_tree (i guess boost.json is another thing). |
The json parser in property tree is a joke. unsuitable for anything serious. |
Absolutely |
Hi,
I've read rationales.md but couldn't find a reference why using json11. When I check their repo I notice that they don't have active development, pull requests from 2014 linger there and dropbox/json11#41 seems like they have performance issues. We like to use ppconsul but json11 from the benchmarks seems unreliable. I wanted to ask you if you had any reasons to choose json11? Thanks.
The text was updated successfully, but these errors were encountered: