What exactly is funny here? The linux kernel is not a userspace library with a public API - and in the case of libuv, judging from `apt-cache search libuv` out

What exactly is funny here? The linux kernel is not a userspace library with a public API - and in the case of libuv, judging from `apt-cache search libuv` output, one which intends to be dynamically linked as well. By exposing this performance-insensitive struct publicly, they're also unnecessarily increasing their ABI surface area. It just reeks of novice library authorship. What makes sense for a monolithic kernel's code is quite different from what makes sense in a userspace library, particularly on its public API boundaries. It's also worth noting that the Linux kernel developers have historically made choices which are actively hostile to kernel module API/ABI stability as a way to discourage third parties from distributing out-of-tree proprietary binary modules. There is literally a policy of not having a stable interface for module writers, it's the anti-library except for the system call interface.