There are pros and cons to the non-/native approaches. Writing effective cross-platform application is harder than one would think. Some time ago there was a d

There are pros and cons to the non-/native approaches. Writing effective cross-platform application is harder than one would think. Some time ago there was a discussion on HN where a WxWidgets maintainer stepped in to explain why some WxWidget programs were apparently inconsistent across O/S, and the explanation was that they were developed naively (I think one needs to use specific spacing abstractions, but I don't remember with exactness). For my personal development, I use non-native (which is easier to develop), however, on large scale, it'd be a tough decision. WxWidget was my favorite in the past (again, for personal development), however, the bindings are very spotty, which prevents adoption for several languages (wiki page: https://en.wikipedia.org/wiki/List_of_language_bindings_for_wxWidgets https://en.wikipedia.org/wiki/List_of_language_bindings_for_...).