Should I learn COM/ATL/MFC?

G

gats2011-09-09 21:37:39

C++ / C#

gats, 2011-09-09 21:37:39

It is clear that the technologies are ancient and our everything will be finished, but maybe someone knows the niches in which the subject is still actively used?

Reply

Answer the question

In order to leave comments, you need to log in

6 answer(s)

A

Alexey Sidorov, 2011-09-09
@Gortauer87

No. It's too old and smells bad already. However, COM seems to be more alive than all the living yet, but here is MFC, it's better not to enter into this byaka.
Yes, and there are excellent frameworks like Qt in C ++

I

igofed, 2011-09-10
@igofed

My teacher, who studied and wrote in MFC for 6 years, said something like this about this time: “6 years wasted.”

Z

Zamorozka, 2011-09-09
@Zamorozka

Here are the areas where it may be required: drivers, support for old software and transfer to new technologies, integration modules.
IMHO, I do not think that now it is used as actively as, say, 10 years ago.

I

ixSci, 2011-09-10
@ixSci

The first is worth it, the second 2 are not.

A

Akson87, 2011-09-09
@Akson87

As far as I know, MFC is still very actively used in many projects. Managed code may be our future, but it's definitely not the real one yet.

K

Konstontin, 2016-04-03
@Konstontin

Hello from 2016!) COM fixes a fundamental C++ problem - the lack of a standardized ABI. The only but - windows only. MFC is still maintained and updated with every release of VS. If you don’t want to carry heavy libraries like QT, wxWidgets with you, and don’t want to write in pure windows API, then the best thing is to use MFC. Despite the fact that the technology is ancient, there are still situations in which there are no other alternatives to COM/MFC.