Slashdot Mirror

← Back to Stories (view on slashdot.org)

Qt vs MFC

Posted by timothy on from the they're-sure-spelled-differently dept.

Philippe Fremy writes: "I have just published and translated into English a comparison between Qt programming and MFC programming, which was written by Pascal Audoux (a fellow coworker). I am interested in feedback and would love to add quotes from developers that have used both toolkits." Here is the English version ("Qt vs MFC") as well as the French one ("Qt contre MFC").

1 of 126 comments (clear)

  1. Notes from a 6-month MFC coder by davidmccabe · · Score: 0, Flamebait

    I haven't used QT, but my experience with MFC has been:

    MFC is the most confusing, bloated, needlessly complex, poorly-designed API in the world.

    First, you use this little program called 'AppWizard', that asks you a few question like if you want toolbars, if you want database support (database support?), if you want OLE, etc. Then it spits out this hulk of code that has all these weird constants and macros in them with names like '__AFX_DEFINED_DDLXCI_AXWEC_UBER_MACRO_EXCHANGE_DD FC' scattered all over it. And you can just pull values out of a dialog box; you have to use this thing called "Direct Data Exchange" that I never really figured out, and you have all these magic cookies that get defined in some header file somewhere and you don't even get to write main() and all the functions have weird names and at least we have a good String class but all the classes start with the letter 'C' and everything is in hungarian notation and all those weird macros and WHERE DO I DRAW STUFF IN MY WINDOW?! and BLAH BLAH BLAH!!!

    I write in Java now.