Is MFC, Com outdated?
-
Hey everyone, I am learning MFC right now and am planning on trying to learn com and ATL/STL. I was talking to a friend the other day and explaining this to him. He pretty much told me this is a waste of my time. That I should learn C# and Java. He was also telling me I should learn .Net. He tells me that C# and java should be easy to learn because I know C++. I am very comfortable with C and C++ and I enjoy coding in it very much. I thought the best way to code gui was in MFC or Com. Is this true, should I not bother with MFC and Com and just go straight to C# and java?
-
Hey everyone, I am learning MFC right now and am planning on trying to learn com and ATL/STL. I was talking to a friend the other day and explaining this to him. He pretty much told me this is a waste of my time. That I should learn C# and Java. He was also telling me I should learn .Net. He tells me that C# and java should be easy to learn because I know C++. I am very comfortable with C and C++ and I enjoy coding in it very much. I thought the best way to code gui was in MFC or Com. Is this true, should I not bother with MFC and Com and just go straight to C# and java?
See my reply in the thread: "Is Visual C++ still alive?" a few threads below this one. To some extent it depends on who your customers are and whether you expect a large number of them to remain on pre-Windows 98 boxes or, if not, whether they object to having the 20MB .NET runtime installed to run .NET desktop apps. In the long run, for customers who stick with Windows, there will be no point in developing anything other than .NET applications. And this will be far easier to do with C# or VB .NET or almost anything except C++. Anonymous wrote: I thought the best way to code gui was in MFC or Com. Is this true It is the best way in that you can get the best-looking GUIs with MFC (or some other C++ GUI framework). However, for rapidity of development, VB is the best way. That's why many businesses increasingly opted for VB for GUI work and used C++ if necessary for data manipulation and calculation. Anonymous wrote: should I not bother with MFC and Com and just go straight to C# and java? You will certainly need to go to one or both of them fairly soon, if not straight away. If you do decide to go to .NET I see little point in continuing with C++ for new .NET applications. But you may need it for migration of legacy C++ or COM code and certain specialised tasks. There will be some .NET operations that can only be done with C++. But, in my view, usage of C++ under .NET will only be in situations where: "if you can't do it in anything else, you can do it in C++" applies. Kevin
-
Hey everyone, I am learning MFC right now and am planning on trying to learn com and ATL/STL. I was talking to a friend the other day and explaining this to him. He pretty much told me this is a waste of my time. That I should learn C# and Java. He was also telling me I should learn .Net. He tells me that C# and java should be easy to learn because I know C++. I am very comfortable with C and C++ and I enjoy coding in it very much. I thought the best way to code gui was in MFC or Com. Is this true, should I not bother with MFC and Com and just go straight to C# and java?
Win32 applications are much faster and have a better performance compared to .Net applications. If performance is not an issue in an application, .Net and Java are the best choices for desktop applications. But for system high performance, visual and graphic applications there isn't any better option than C++ and Win32 or MFC. Good Luck!