Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

FragStorm

MFC vs. C++ Builder

This topic is 6698 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I am sure this has been asked many times, but I glanced through and couldn''t find it. I by no means intend on starting a war over this, but I plan on starting to get into more advanced GUI code than standard win32. So I was wondering if I should go out and learn MFC, or go out and learn C++ Builder , ( or something else? ). I know you will say that is your personal preference, but what is the real advantages between the two. I hear many people bash MFC, but I hear many people ''like'' it too, and I hear many people like C++ Builder also. I simply want to create the most efficient GUI applications, and am searching for a clear answer in which direction would be best to take. I am willing to learn either one, as I''m sure it won''t take long to learn either of them. Thanks, and Don''t blame me if this starts a war between Russia and America We shall be free; th'' Almighty hath not build here for his ervy, will not drive us hence: Here we may reign secure and in my choyce To reign is worth ambition though in Hell: Better to reign in Hell, than serve in Heav''n.

Share this post


Link to post
Share on other sites
Advertisement
Well, if you''ve ever used Visual Basic, then it''s about the same as C++Builder supposedly (I''ve never used VB, but I used to use C++Builder). It''s a very nice compiler, with a very nice, efficient framework. If all you want to do is GUI apps, then it''s certainly a good buy. Although, I think most businesses use MFC, so it depends on if you want experience that will help you in the real world. I''m not sure if that matters though...

------------------------------
Jonathan Little
invader@hushmail.com
http://www.crosswinds.net/~uselessknowledge

Share this post


Link to post
Share on other sites
Yes, most businesses use MFC.

I started Win32 programming with MFC, but got stuck with the Data/View things. Then luckily I found a great site, Reliable Software, which have tutorials on using win32 API. Hmm... now I can go further than using MFC.

MFC basically hide away thousands lines of codes behind a casual programmer (like me ). If you say an efficient GUI app, then win32 API is the better way to go. I''m not saying that MFC is bad... I just can''t work like the way MFC expected me to do.

If you want an easy-to-use framework, go for C++Builder. I''ve tried it before and I must say it''s faster to develop. And it''s going to have a Linux version out too.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
At work we use Builder because it''s faster at producing the interface programs we need. My own personal preference would be to use MFC because most other places use it but at home I still use Builder for my projects. This is mainly due to it''s speed and ease of use.

Share this post


Link to post
Share on other sites
Well, if you want to create the most efficient GUI application, you really shouldn''t be using MFC *or* VCL (C++ Builder''s windowing library).
That being said, I haven''t noticed much difference in terms of performance between MFC and VCL. And if you want to bypass the functionality of either, the window handles in both are freely available for those direct API calls.

Personally, I prefer C++ Builder. I think the interface to VCL is cleaner and more intuitive. (Just talking programatic interface to library functions here.) And creation of GUIs is a breeze. On the downside, VCL is implemented in Object Pascal, so sometimes you''ve got some wierdness with regards to inheritance and constructor calls. Another downside is that not as many people have C++ Builder, so it''s harder to share code. (Although some popular projects are based on C++ Builder, litestep, for example, comes to mind.)

MFC is, of course, better to have on your resume almost everywhere other than when I''m doing the interviews. There''s a lot more support available for MFC (then again, it''s also more necessary for MFC). On the downside, I think the API is a mess in terms of architecture, and whoever thought up standardizing the Document/View model should have their kneecaps broken. I think the whole thing suffers from feature creep/bloat. (VCL in comparison is very focused on delivering access to UI components.)

Share this post


Link to post
Share on other sites
Alright. Thanks everyone for the advice. I think what I''ll do first is go on the net and search for some good MFC tutorials and see how I like it... If not, I''ll use C++Builder. Or maybe I''ll just use both

We shall be free; th'' Almighty hath not build here for his ervy, will not drive us hence: Here we may reign secure and in my choyce To reign is worth ambition though in Hell: Better to reign in Hell, than serve in Heav''n.

Share this post


Link to post
Share on other sites
For MFC resources and information, try www.codeguru.com

I happen to like MFC, because I''m good at it. I haven''t had problems with the limitations because I ignore them and write my own custom controls *grin* Granted it''s slower than something like DirectX, but for a business app, close enough.

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!