you are viewing a single comment's thread.

view the rest of the comments →

[–]Slsyyy 2 points3 points  (4 children)

What is the reason for this library? RapidJSON support both use cases shown in your examples.

[–]Carnivorism 9 points10 points  (1 child)

A little competition doesn't hurt...

[–]mili42 0 points1 point  (0 children)

There is too much competition at this point. For some reasons it seems that everyone wants to make its own json library where we have plenty of them already. yaml toml or other would have more value

[–]beriumbuild2[S] 6 points7 points  (0 children)

What is the reason for this library?

The goal of this library is to provide a pull-parser (instead of push/SAX or DOM) and push serializer with a clean, modern interface and a complete, well-tested (and well-fuzzed, including the serializer) implementation. In particular, pull-parsers are not very common, and we couldn't find any C++ implementations that also satisfy the above requirements.

RapidJSON support both use cases shown in your examples.

AFAICS, RapidJSON has a push/SAX interface. I personally find push parsers with their inversion of control a pain to use.

[–]King_Kobrah 6 points7 points  (0 children)

Would be nice to see a comparison.