2 ms·
Because it's not good. It is neither consistent ("CreateWindowEx" style naming versus "Shell_NotifyIcon" versus "CDefFolderMenu2_Create2" (huh?) versus "CreateT
by pcwalton 11y ago
Because it's not good. It is neither consistent ("CreateWindowEx" style naming versus "Shell_NotifyIcon" versus "CDefFolderMenu2_Create2" (huh?) versus "CreateToolhelp32Snapshot" (huh?!) versus COM), documented enough to engineer independently (witness all the strange behavior Wine has had to reverse engineer), or powerful (fork is officially unsupported, despite being supported by the NT kernel).
- douche 11y agoYou're looking at a code-base that evolved from 16-bit to 32-bit to 64-bit over 25-30 years, and 10-15 major releases. You've got the 95/98 code base merging with the NT code base. You've got all the compatibility fixes that Microsoft has invested in to try to help old, poorly written code continue to work. It's accreted some cruft.
- pcwalton 11y agoI'm not blaming anyone for the APIs being in the state that they're in. I'm simply saying that the Windows API is, today, taken as a whole, a more crufty API than the Web APIs are.