libclang is a library, clangd is an executable. That post is about switching away from libclang-based tooling infrastructure; i.e. stop developing their own tool.

There differences in C wrapper vs C++ are superficial and not what this blog post is about. The problems are rather with the poor division of labor between the intermediate represents and the lies that they are properly self-contained. This is about what clang does, irrespective of whether one slaps a C interface on top or not.

You wouldn't 'execute' clangd. You would send it messages adhering to its Language Server Protocol [1]. The distinction between library API and server API is small. Moreover, Apple switched away from libclang-based tooling towards clangd.

[1] https://microsoft.github.io/language-server-protocol/specifi...

I can't tell if you're trying to split hairs or just being unintentionally obtuse. How do you propose sending clangd messages without executing it, i.e. starting the language server?