2 ms·
You're probably right that applications still using Win32 directly are unlikely to switch to anything new. But the other frameworks you mention seem to be more
by wtallis 8y ago
You're probably right that applications still using Win32 directly are unlikely to switch to anything new. But the other frameworks you mention seem to be more than just wrappers; they're relatively heavyweight application frameworks that bundle a lot of new functionality rather than just providing a cleaner interface to the core Win32 functionality.
It seems like there should be some appeal in a clean modern Win32 API wrapper that compiles down to almost nothing and doesn't impose design decisions like using XML to define UI layout. That would allow higher-level frameworks like UWP to be implemented in a dialect that isn't so disgustingly arcane.
- cl0ckt0wer 8y agoIt sound like you want a wrapper that does nothing but change SHOUT to CamelCase. A lot of work to for a developer only cosmetic. What are you doing in UWP that's arcane?
- wtallis 8y agoPlease read more carefully; I think you missed the point of more than one comment in this thread, so your reply comes across as too dismissive. A modern wrapper around Win32 would offer real advantages beyond just renaming things, such as greater type safety and less namespace pollution. And I didn't imply that such a thing would have benefits for authors of UWP applications, but for the implementors of UWP itself and other frameworks that build atop raw Win32.