3 ms·
It wasn't always like this. The Windows API was fairly stable from the mid-late 90s for at least a decade. They decided to start breaking that compatibility in
by taneq 11y ago
It wasn't always like this. The Windows API was fairly stable from the mid-late 90s for at least a decade. They decided to start breaking that compatibility in the name of 'progress' at around the time they started trying to squidge together their touchscreen and desktop interfaces, but this API stability used to be one of the huge drawcards of the Windows platform.
- pjmlp 11y agoMy Windows coding experience goes back to Windows 3.0 and I am looking forward to the day Win32 and Hungary notation are nothing more than plain maintenance coding, replaced by a proper type safe OO ABI like WinRT.
- userbinator 11y agoMy past experience with others "OO-ifying" APIs (e.g. MFC) makes me think that'll just end up being worse because it tends to add a lot of complexity that gets in the way and obfuscates the flow of the code. Besides, Win32 is implicitly quite OO already and can be used from a variety of languages because it's based on C. Not everyone wants to use C++.
- pjmlp 11y agoMFC is not a good example. OWL, VCL are much better approaches to Windows frameworks. Not everyone wants C to stay around.