> It's unfortunate that a UI layer ties you into a particular programming language I think it is unavoidable that it ties you to a programming language paradig

> It's unfortunate that a UI layer ties you into a particular programming language I think it is unavoidable that it ties you to a programming language paradigm. For example, it may assume the existence of booleans, reference counting, garbage collection or of multiple inheritance. If your preferred language doesn’t support them, that will make the bindings look uglier than needed. Conversely, if your preferred language supports them, but the API of the UI layer doesn’t, the bindings will look cumbersome in places where using those features looks natural. So, what you end up with is either plain C (ugly for everybody, including C programmers, even they may not want to admit it), C++ or the JVM, or something like it that looks fine for C respectively C++ respectively Java programmers but feels strange in some degree to others, the more so the less their language ‘feels’ like C respectively C++ respectively Java, or COM/SOM/CORBA, which claim to be language agnostic, but don’t do that for the feel of an API.