alt Hacker News> That said, these rely on USER.32.DLL and KERNEL32.DLL to do the majority of the heavy lifting.
Since the low-level Windows kernel API is undocumented and non-public, using these system DLLs is your only option on Windows.
It's just like linking against libc.so on any POSIX systems.
no, you can also call ntdll (or even syscalls although those aren't stable), there's plenty of documentation on the internet
but also why would you, not much point except for very niche functionality