I preferred the native Windows API[^1] from the point of view of organization. In theory, you could use it to design the data flow in your application in whiche

I preferred the native Windows API[^1] from the point of view of organization. In theory, you could use it to design the data flow in your application in whichever way you wanted. And yes, the operating word is "design", meaning that you needed to be decent at architecting software. And this was before .Net and before many C++ facilities that would make life easier (e.g., std::shared_ptr, or even boost::shared_ptr), when making a large scale application in C/C++ required some serious chops I was too young to have. [^1]: https://learn.microsoft.com/en-us/windows/win32/winmsg/using-messages-and-message-queues https://learn.microsoft.com/en-us/windows/win32/winmsg/using...