Originally posted by kraftman
View Post
Qt is also oddly slow, did you try to make a small with application using QWidgets and try to compare it with Xaml/WinForms stack? Try to make a project with 10 forms and first form starts the second and so on, and try to see how much asks for a build/rebuild cycle. And use Mono for the same thing. Use Python for the same thing.
As for me, Mono is somewhere in between: 80% of C++ performance, 10x shorter compiler times. As tooling, reflection is really cool to be used and works from scratch! Try for fun to setup an unit test and to run it using QTest and compare to NUnit/JUnit.
At the end, try to profile your application: in .Net or Mono you have sampling profiler pro bono. C++? Valgrind... (aka running things 10 times slower to find leaks), KCacheGrind (running 10 times slower to find a profile session). Running things under profiler in Mono/.Net!? 10-30% drop in performance but that's it!
In the meantime, I am just thinking how fun is to write a multi-threaded application in C++/Qt: memory corruptions, more inconsistent memory managers (QObject memory model, boost smart pointers, Stl auto_ptr, your own management, stack and heap pointers/.Net world is mostly heap and stack), memory leaks, and you add some minutes compile time... absolutely fun, as you try to understand the template errors.
Yet is possible to write in Qt a simple web service consumer/producer, without a need of XSP (which comes with Mono package) that offers a lot more fun.
Comment