Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I wonder if my perception on this subject is correct. Is there any point of using embarcadero’s C++ builder (now with their compiler based on clang) and FireMonkey framework in favour of Qt? The point is that Qt seems to be leaving widgets behind and they are concentrating more on javascript, while embarcadero seem to be very commited to C++. Am I right or I see things incorrectly?
Thank you.
No. From Qt 5.0 onwards the push is for GUIs to be written in QML whilst the backend is still whatever you want it to be (C++ traditionally, but there are Qt bindings for almost language). The primary reason for this is because writing modern fluid hardware accelerated UIs is quite laborious, so Qt have written a JavaScript-based language that automates much of it; the other reason is because although everyone knows that GUI code and backend code should be totally separate, in the real world over time they tend to become mixed, having a QML frontend with a signal/slot driven backend enforces this.
Also Qt have all the ‘traditional’ widgets available in QML (currently still in beta but aimed for release for v5.1 – I think), and the C++ widgets will still be available in their own library. Not to mention the fact that Qt always supports the previous version, so you’ve probably got another 7 years for ‘normal’ v4.x C++ widgets!
I cannot comment Embarcadero or FireMonkey – because I have never heard of them…