I like how in Win32...

...you have to populate three structures, allocate two output buffers and call four API functions to fucking ring a bell. Then everything works with handles. You have a faphandle to fap, a dumphandle to take a shit, etc. Data types such as "int" are aliased to funny names like EUAOPFGHVNUMBER, and parameters have hilarious Hungarian notation such as lpszFetus, and there are millions of them. You end up writing function calls vertically.

It's all like HFAP WINAPI CreateHandleForFapping(HHMNPART hhandWith, LPSTFUCK stWhoareyoufapping, SSECURITY_ATTRIBUTES ssaNobodyaround, SSEXTRASECURITY_ATTRIBUTES ssChurchToken, NULLTYPE nReserved).

>>1
nobody's forcing you to use the shitty hungarian notation for variable names that they use in the docs. well, i guess you end up using them when you're pasting a gigantic function prototype with 32 parameters from the SDK documentation.
... and the typedef madness has enabled them to keep the same APIs from windows 1.0. (okay maybe that's not a good thing)

the win32 api seems to follow a "less work for the API coders, more work for the API end-users" philosophy...