A toolkit like this is only another option in your basket if you can ignore real-world considerations like: - Internationalization: The edit control doesn't su

A toolkit like this is only another option in your basket if you can ignore real-world considerations like: - Internationalization: The edit control doesn't support input method editors. On Windows, wide-character functions aren't used; that means Unicode isn't supported. - Accessibility: Here I'm talking about the ability for users with disabilities, most notably blind users but also users with mobility impairments, to access a UI via assistive technologies such as screen readers or alternative types of input. This requires the GUI toolkit to implement an accessibility API such as Microsoft Active Accessibility or UI Automation on Windows, or AT-SPI for X11-based environments. This is something that practically everyone who sets out to implement a lean, mean, simple toolkit just doesn't pay attention to. - Native look: The toolkit doesn't attempt to mimic the look of the rest of the system at all. On my Windows 10 machine, the demo looks like a throwback to Windows 95. This is also an accessibility issue, for low-vision users that need a different color scheme. And there are probably other considerations I've forgotten or am unaware of. You'd probably be better off using one of those big, bloated C++ toolkits, like Qt or (better yet, IMO) wxWidgets. Not GTK, since that doesn't cover accessibility except under X11 via GNOME.