serializer VS json_test_data

Reference to the "old" C++14 library zpp_serializer, I didn't want to update this one since it could create a lot of complexity to work between these C++ standards.

>Maybe take a shot at parsing JSON in C++ and see if the nostalgia survives the process.

I have used this library in the past and was actually pretty easy

https://github.com/nlohmann/json

https://github.com/nlohmann/json

I used this for JSON last time I wrote any C++ a few years ago and it still seems popular. It seemed sane enough to me.

On the other hand, I'd like to bring in the json library of my choice, e.g. https://github.com/nlohmann/json or https://github.com/danielaparker/jsoncons. So I'd prefer the web server library provides as little as possible in the way of Json support, and certainly doesn't get in the way of using my library of choice. Similarly, I'd like to use my choice of automatic object serialization.

I find openMVG very decent, FTXUI might be a good one and nlohmann's json library is also pretty nice. I don't really know of any project that strictly adheres to the core guidelines, except maybe for some of Jason Turner's (sample) projects.

JSON for Modern C++. Intuitive syntax. Trivial integration. Serious testing. Memory efficiency. Speed.

Please provide us an example of this one minute process you talk about for an example project of opening a JSON file, writing to it and closing it with a library like `nlohmann`s.

Use a small library like this: https://github.com/nlohmann/json

I worked on my partner’s static site generator, rwar, to implement this feature and she worked on my static site generator – palpatine. I was easily able to do this in rwar which is written in Python. However, I realized that this feature was much harder to implement on palpatine which is written in C++. Samina reached out multiple times seeking help for the broken Cmake configurations and for helping in integrating the nlohmann/json library.