[1]: The C Programming Language (2nd Edition) [2]: POSIX.1-2017. https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/ https://pubs.opengroup.org/onlin

[1]: The C Programming Language (2nd Edition) [2]: POSIX.1-2017. https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/ https://pubs.opengroup.org/onlinepubs/9699919799.2018edition... [3]: The Linux man-pages project. https://www.kernel.org/doc/man-pages/ https://www.kernel.org/doc/man-pages/ [4]: Apple Documentation Archive. https://developer.apple.com/library/archive/navigation/ https://developer.apple.com/library/archive/navigation/ [5]: Windows API index. https://docs.microsoft.com/en-us/windows/win32/apiindex/windows-api-list https://docs.microsoft.com/en-us/windows/win32/apiindex/wind... The age of the documentation has absolutely nothing to do with using the software. I highly encourage developers to get rid of this mindset. Generally it comes from younger developers who have less exposure across the board. Senior developers should be comfortable reading standards documents and knowing that they will be years old. They are old for a reason. They stood the test of time. Read your man pages. Eat your vegetables.