Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Edit: This answer was written in <em>2008</em>. It probably is no longer so apt, though probably it is not entirely useless. Take with salt.</strong></p> <p>I have used both and have ended up going the Qt route. These are the reasons:</p> <ul> <li>Trolltech offer quick and one-to-one support via email</li> <li>Qt innovates, and introduces powerful new features regularly</li> <li>The Qt documentation is amazing, and in the rare cases where it isn't, you can read the source code</li> <li>Having the source code for Qt also allows you to debug inside your base libraries, which has been a life saver for me on many an occasion</li> <li>The API is very consistent and well designed. We have put new people on the project and within a month they show deep knowledge of the toolkit and can learn new classes very quickly</li> <li>It has bindings to other languages, eg. Ruby and Python.</li> </ul> <p>C++ is somewhat of a downside, eg. compile times, packaging, and a less integrated IDE. However Qt does make C++ feel more like a higher level language. QStrings take all the pain out of string handling for example. Thus the additional issues with C++ that you would normally face, eg. more buggy code, are less prevalent in my experience when using Qt.</p> <p>Also, there are more libraries for Delphi than for Qt, but this is mitigated due to the fact you can just use a c or c++ library in a Qt project, and also because Qt is so fully featured you often don't have to look any further.</p> <p>It would be a strange situation where I would choose Delphi over Qt for a new project.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload