I mean, as far as I know, most would still implement this the same way. Surely there could be a GUI framework that'll handle these Win32 Messages and dispatch

I mean, as far as I know, most would still implement this the same way. Surely there could be a GUI framework that'll handle these Win32 Messages and dispatch them to your callbacks in your `Application` object but your application could be dealing with all sorts of messages not covered by your framework like WM_SYSCOMMAND, WM_POWERBROADCAST, WM_DEVICECHANGE, etc. and you'll find yourself with this classic Win32 Message Queue handling switch even in modern C/C++ Win32 GUI codebases. Whenever you are interfacing with the Win32 API directly to set up and run a GUI application, this pattern will emerge: https://gist.github.com/nathan-osman/18c2e227ad00a223b61c0b3c16d452c3#file-win32-go-L195-L204 https://gist.github.com/nathan-osman/18c2e227ad00a223b61c0b3...