Interesting. The C++ JSON parser by Niels Lohmann that is a more or less defacto standard seems to parse things wrong, or at least give out wrong value when getting named values from a nlohmann::json instance. Very weird, as it used to work ok. Oh well, time to find something else then.

#json #nlohmann

First time I'm properly using the nlohmann JSON parser for C++. it works using rocket magic and at least I have no idea what the code actually does by looking at it. :) But when you do something wrong you're in for hellish templated error messages that make no sense. But so far parsing some config files is a real breeze. I just wish C++ had a string library that didn't suck monkey balls through a paper straw.

https://github.com/nlohmann/json

#cpp #json #nlohmann #monkey #balls

GitHub - nlohmann/json: JSON for Modern C++

JSON for Modern C++. Contribute to nlohmann/json development by creating an account on GitHub.

GitHub
Building RESTful Interfaces in C++ With nlohmann and cpp-httplib – Kevin Carpenter – C++ on Sea 2023
https://www.youtube.com/watch?v=uqPTzUdNLZk
#coding #cpp #nlohmann #programming #REST #softwareengineering
Building RESTful Interfaces in C++ With nlohmann and cpp-httplib - Kevin Carpenter - C++ on Sea 2023

YouTube

I switched the #JSON loading library from #NLohmann to #RapidJSON and now a single asset loads in 12 ms instead of 14 ms.

I mean... 12 is definitely less than 14.

In the large scene with about 300 assets that makes... 600 ms faster loading times! Woohoo!

#performance #cpp #gamedev