RapidJSON VS libuv

Here's what I did: - I bought a theme that I liked, and used mstch as template engine (matched the theme's template format) - Imported rapidjson for parsing JSON, and used mstch for generating JSON (the JSON I generate is simple enough that I can do this) - Wrote an HTTP handler class for each page that handles the GET and POST requests, generating HTML or JSON depending on the request

And documentation in most cases is more user-friendly if you will use something like MkDocs(based on Markdown), example http://rapidjson.org/

Use RapidJSON https://rapidjson.org/

It seems not super widely used compared to other famous libraries like RapidJSON, nlohmann-json, or simdjson. But it seems the author is very active in developing this project which can mitigate this "lack of community" issue.

have a look at rapidjson for a a nice simple json framework https://rapidjson.org/ I use it and it's quite fast and as good as anything I used in python.

So I just cloned https://github.com/Tencent/rapidjson to see what is the current status. At compile time they check if the C++ compiler supports the "noexcept" keyword, and if so they define RAPIDJSON_NOEXCEPT to be "noexcept". Throughout the implementation, RAPIDJSON_NOEXCEPT is added to quite a few function declarations (about a hundred of them).

RapidJSON is also excellent, like fantastic when performance matters. Not sure there's a much faster JSON implementation anywhere, and I've written my own SAX-style parser as a fun, hobby project for C++.

I wound up on a different team with pre-existing Python code so temporarily shelved my use of Go for a bit, and we used Sanic (an async Python framework built on top of the excellent uvloop & libuv that also powers Node.js) to build some APIs for live channel management & operations. We hand-wrote our OpenAPI and used it to generate documentation and a CLI, which was an improvement over what was there (or not) before. Other teams used the OpenAPI document to generate SDKs to interact with our service.

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Libuv, the C library that gives Node.js its asynchronous, non-blocking I/O capability is responsible for managing the thread pool. Node.js gives you the capability of using additional threads for computationally expensive and long-lasting operations to avoid blocking the event loop.

Node.js is written in C, C++, and JavaScript. The core components of Node.js - the V8 engine and the libuv library - are written in C++ and C, respectively, since these languages provide low-level access to system resources, making them well-suited for building high-performance and efficient applications. JavaScript is mainly used to write the application logic.

x8 apparently https://github.com/libuv/libuv/pull/3952

Notably upgrades to libuv 1.45 which has io_uring support. Faster file system access! Awhh yeah, it's on.

Remarkable what a mild & unintrusive PR adding io_uring was. https://github.com/libuv/libuv/pull/3952

Well, the single-threaded nature ultimately leads to its biggest downfall. Node.js utilizes a synchronous event loop engineered using Libuv that takes in code from the call stack and executes it.