>>78
First of all, WinAPI uses the BSD socket interface which is what POSIX standarizes. WinAPI modifies the function prototypes to mismatch (char * instead of void*!), changes ssize_t et cetera to its own types (which are both redundant and god-awful), adds its own set of functions that are related to networking, but makes them mandatory in the sense that you can't write code without them (WSAStartup et al), adds bloat like 'closesocket', does not provide access to raw sockets (sendmsg, recvmsg, ...). That alone should tell you why POSIX is superior for networking compared to WinAPI. Now imagine this for everything WinAPI provides: Microsoft made it bloater, suckier, incompatibl-er with competitors, etc. WinAPI also defines a lot of functionality that according to some should not be part of a standard API for developers. POSIX is almost an extension of C (with some exceptions, for example C says CHAR_BIT >= 8 while POSIX says CHAR_BIT == 8). WinAPI is a different language altogether, with its own types, errors, stupdiity, et cetera.