json-c VS rapidyaml

When you say .jsonc, do you mean JSONC, JSONC, or JSONC? And have I mentioned JSON-C?

to manipulate JSON data: https://github.com/json-c/json-c (I haven't used that one personally but it looks good)

If you want a comfortable developer experience without having to "develop standard functionality," choose another language.

Otherwise: libcurl for the requests, json-c[0] for the JSON handling. SDL for window handling/events/other glue stuff. I don't know what rocksdb is but I assume it has its own C API library.

[0]https://github.com/json-c/json-c

There’s also json-c and Hjson.

Yes. This library does basically that: https://github.com/json-c/json-c

$ git clone https://github.com/json-c/json-c.git $ mkdir json-c-build $ cd json-c-build $ cmake ../json-c

Look for the instructions here: https://github.com/json-c/json-c

Interesting, I hadn't come across extism before. How hard would it be to package https://github.com/biojppm/rapidyaml in this way? (And do you have a extism for dummies guide?)

The inability, or brittleness, to embed NUL bytes into the string, for once. Zeroed bytes can be valid as an internal bytes of a longer encoded character. And the inefficiency of tempting every caller to rederive the string length on every use, leading to such bugs as quadratic parsing behavior with sscanf. The extra register for an explicit length is a very minute price to pay compared to that.

Although you still have the other problem of sscanf, where read times can become quadratic.

You are really simplifying that issue. A lot of it has to be how the implementation of sscanf works and it's super easy to abuse by complete accident when a lot of data needs to be read and parsed to correct values. See more here: https://github.com/biojppm/rapidyaml/issues/40

Leading to eye-rolling problems like these: https://github.com/biojppm/rapidyaml/issues/40