You could use Xlib to program a client in pure X11, but that approach would have been outdated even 15 years ago. There's no good reason to do so today, even embedded systems often use Qt and there's good support for building embedded/Qt in Yocto. Most embedded devices that have any UI at all are likely powerful enough to run Qt, so I suspect there aren't many cases these days where you need to limit yourself to Xlib because of performance.
Xlib is actually not very pure X11; Xlib makes a lot of things synchronous whereas X11 is really an asynchronous messaging distributed systems protocol that happens to output to the screen as a side effect. Xcb is a much closer to the actual protocol library.
IMHO, a lot of early hate for X11 was really hate at Xlib; but as Xlib was the official library, it was understandable to get them confused.
Things are slowly shifting to Wayland.
Never fully used by all, old hardware around for decades without it, and likely require something else, such as X11 now supports wayland!
Just as I suspect ipv8 will make ipv6 disappear!
ipv8 is identical to ipv4, it just has another 256 in front of it. 5 octlets. A 6th octlet for planet designation...
Very few would bother to do X11 graphics directly with Xlib, we aren't in the 1980's.
[0] - Some would say Vulkan I rather spare myself the burden.
2122 of course.
X11 forever!