Discussion on:
Message 9 of 1
@John Zern Why ask a question directed at DonnieBoy and then answer yourself in the same post? When/if someone replies with one a several reasons why the Win32 api could be classified as "nasty", you'll just look more the fool. The fact is the Win32api is not universally coded to a specific standard, programmers have to accommodate Win3.1, WinXP, Win Vista, and later, they are expected to code for 32bit and 64bit versions, plan around various versions of .Net, and certain older libraries, some new ones, create dependencies on specific versions of IE. While this is something developers have come to expect, I could see it being described as "Nasty" in terms of porting applications to a non-Windows environment.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
