Is MFC dead?

In the past few days, I have discussed with a few foreigners what programming languages I use in the Forum. To my surprise, people like me who have been using MFC for more than 10 years have become monsters in their eyes. In addition, they recommend C # In the same voice #. A foreigner said that his previous project used MFC at the beginning, but the progress was very slow. Later he switched to C #, And the development speed increased by an order of magnitude. He thinks that C # is the easiest way to use. C # is his first choice.

As we all know, C # is implemented by Ms to combat Java. C # I have never used it, but I have been using Java for a while. I heard that C # is pure OOP and even Int. I also heard that JIT can convert the msil generated by C # to 100% local code, so that C # runs faster than Java on Windows. C #'s simplicity and security allow it to get started quickly, reducing development and maintenance time. C # is good. In this case, you can use C # to write programs. The old and hard-to-learn class libraries like MFC disappear. This is my real idea. I think I spent a few days writing a control in MFC, and people completed it in minutes in C. Does MFC really make stinky tofu? I guess it's time for me to switch?

 

As a result, I searched Google and Baidu for the following keywords: "still using MFC" "MFC dead" "MFC dead" ...... This is true. In the search results, most of the posts are from. That is to say, many people thought that MFC was not going to work in. Over the past two years, we have not discussed it much. We may think that MFC is dead. I even immediately used depends to view all the programs under my computer C:/program files and how many MFC programs were used. It's strange.

 

Is MFC really dead? The answer is: no, and will not die for a long time.Maybe I did not believe this last year, but when the new MFC class library appeared in vc2008, after the vc2008 Feature Pack of tr1 was released, I think all the MFC programmers should be excited (just as if they had been infected with chicken blood.

//////////////////////////////////////// //////////////////////////////////////// /////////////////

Sorry, I'm sorry. We (Windows programmers) are only a poor team who survive in the ecosystem created by Microsoft. Microsoft plays the role of God. Look at you, poor, give you a good tool (such as C #) so that you do not have to write programs so hard. Look at the MFC, the ax is rusty, and it is taken for grinding, and then the "State" is chopped on the wooden pile, immediately surrounded by a bunch of old, poor, and moved tears that cut trees with MFC.

//////////////////////////////////////// //////////////////////////////////////// /////////////////

Indeed, since the unprecedented success of the vc6 release, the MFC is like a child that has no one to raise, and has been running out until vc2008. (Now many companies are still using vc6. Well, there are still well-known companies here ). Over the past few years, Ms has put most of its energy on. NET and C. Because powerful competitors come from the network rather than the desktop field.

 

Let's take a look at the poor MFC, a veteran who has made great contributions to Ms since the beginning of 1990s, because of some criticized designs and steep learning curves, and of course there are poor UI functions, more and more become chicken ribs. I think most programmers who still use MFC were born 85 years ago, right? Like when I graduated from college ,. net and C # are the first to come. VB is reserved for girls (Sorry, VB programmers, joke). Delphi root is not red, Miao is not correct, and desktop programmers only seem to have to go through the well-known path of MFC (high salary). Later, we found that MFC was actually a steep cliff. Some people rolled down, and some people made a helicopter. Many people had no choice but to climb up. How proud we were when we climbed to the mountainside (or mountain bag), overlooking the mountain. To use MFC, you must understand windows
API, Windows message mechanism, DLL, com ...... I think it is too simple for MFC programmers to start using VB and C #. There is no difficulty, and objects do not need to be deleted. It is a little impractical to look for controls directly if you want to use them. I can't help asking, is this still programming? Is it a dream? Return to MFC and start a line of code writing. After the new delete operation is completed, several APIs are provided from time to time, or even embedded with ASM. This is my habit of programming. It seems that I am out.

 

I have always had this idea. I don't know, right. Languages like VB and C # Abstract programming languages to a very high level, which is a double-edged sword. The good thing is that many Middle School Students can write programs. The bad thing is that more and more programmers can only write programs at this level. When they return to C/C ++, it will be very scared. It's like you got into a bread from a Mercedes-Benz. Who will write a program like the. netframework runtime environment? Msmsms continues to act as God.

 

Microsoft Foundation Classes

I don't know if it is because of this name. MS will keep you alive.

 

BTW: Maybe I will become a C # programmer one day, followed by MS, with meat to eat...

From address http://blog.csdn.net/superjoel/article/details/4062509