> See also Linux's nolibc headers
Kind of an understatement. The existence of an official interface obsoletes 3rd party projects like the one posted.
nolibc seems very minimal. For example, no pread/pwrite just read/write, forcing you to lseek and ruining concurrent use.
Ya totally - those wacky people at chrome must've just never heard of those headers /s
What you don't understand, because you don't work on Chrome, or Chrome sized projects, is that generic, lowest common denominator implementations cannot be optimal for all use-cases and at scale (Chrome-sized project) those inefficiencies matter. That's why this exists, that's why folly exists, that's why abseil exists, that's why no not everyone can just use boost, etc etc etc
Might be a license thing? The Linux headers are probably GPL like the rest of Linux.