json_test_data VS gui_starter_template

>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.

Was checking that as well, can't find it indeed. I would recommend looking into the following: https://github.com/cpp-best-practices/gui_starter_template

gui_starter_template. This is a C++ Best Practices GitHub template for getting up and running with C++ quickly.

Next to language versions, spend time setting up your build system (CMake?) with all bells and whistles. You want unit tests, clang-tidy, include-what-you-use, sanitizers, fuzzing, clang-format, package managers. Just take a look at https://github.com/cpp-best-practices/gui_starter_template

https://github.com/cpp-best-practices/gui_starter_template from Jason Turner (aka lefticus) is quite a popular one (2.1k stars in Github)

I actually just tried to play around with what seems to be a "modern c++" boilerplate project.

It uses CMake, conan for packaging, clang-tidy and cpp-check, and has templates for fuzz and unit testing[1].

I found it because qtcreator and kdevelop were weirdly clunky and created partly broken qt projects and I figured I wanted to add a package manager and qt to the mix.

The template looks really fancy, but it's so incredibly slow, to the point of being unusable.

It's a ramble yes. But the point is modern C++ tools seem to have added some niceties to the language, but they also brought more of the main C++ issues, i.e. slow compile times and nasty boilerplate in the build process. Yes, I realize CMake isn't modern and there are a bunch of new build tools.

[1] https://github.com/cpp-best-practices/gui_starter_template

Clang-tidy file of the C++ Project Template

For cmake i find this useful: https://cliutils.gitlab.io/modern-cmake/ https://github.com/cpp-best-practices/gui_starter_template

Jason Turner (known from cppcast) has following project: https://github.com/cpp-best-practices/cpp_starter_project

this is a cpp_question, but anyway, I think this is exactly what you're looking for. Credits go to Jason Turner.