json_test_data VS CppCoreGuidelines

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

If you aren't aware of the c++ core guidelines[1] - it should be on your radar.

Also, it might not be a popular opinion, but I think Bjarne's books are just fine.

A Tour of C++ (3rd edition) [2]

Principles and Practice Using C++ (3rd Edition) was just published in april 2023 [3]

[1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.