What's wrong with DCOM?

Question

There seems to be a lot of enmity against DCOM, and I'm curious to understand why. For a company still writing to the Win32 SKD using C++, is there any real reason not to use DCOM in current or future development? Is some future version of Windows not going to support it? Is it too fragile and fails to work often? Is it too complicated to implement compared to other technologies? What's the deal?

Answer 1

I dislike COM/DCOM because "Catastrophic failure" is the most unhelpful error message in the history of error messages.

Answer 2

1. Security model. Especially when computers are not in the same domain (or aren't in domain at all).
2. Auto interfaces modeled for Visual Basic (original, not .NET), obsolete and not pretty to use from other languages.

If you only want to develop in C++ and deploy in controlled network, it may still be a good choice.