Keep in mind that you have created a strawman by extending the requirements of "deploy everywhere" to be UI-focused, when one-size-fits-all UI is not listed as

Keep in mind that you have created a strawman by extending the requirements of "deploy everywhere" to be UI-focused, when one-size-fits-all UI is not listed as a selling point. In the case of HaXe, its focus has emerged from Web games with server-side needs, where UI is primarily a concern on only one platform, or shared between two platforms(Flash and JS/HTML). Although there are now several haXe libraries that are willing to suffer the "slings and arrows" necessary to provide a flexible API experience, the core language is very realistic about what it is going to provide across all platforms - a limited set of data, logic, and networking compatibility. In all other respects the language is very, very concerned with being able to drill down to the native features of each platform and achieve as native an experience as possible given the constraints of a garbage-collecting, dynamic/static mixed, classy OO language design.