Perhaps he did all his COM programming in C++?
Over the last 6 months I happen to have had two engagements that have
required me to do COM and C++ again.
It made me realize I'd forgotten just how less productive it is than
.NET.
And it's specifically a language thing, rather than a broader tooling
issue. C++ COM code requires you to write about three or four times as
much code as you would in C#. And there are lots of extra ways it can go
wrong, so you end up spending so much more of your time and effort
having to think about things that are absolutely nothing to do with the
problem you're actually trying to solve.
I'd forgotten how painful C++ COM was. (Although this is more a C++
issue than it is a COM issue. There are languages in which COM is
pretty easy to use.)
--
Ian Griffiths
-----Original Message-----
From: Frans Bouma
> Sorry, I was only joking, I do not suspect the framework is crazy.
I know, Paul ;)
> My COM days are thankfully a distant memory!!!
I don't understand this that much, but perhaps you had a
horrific experience with the wonderful world of COM and DCOM and I
can fully understand you therefore are happy with every millimeter you
can get away from it ;)
FB, who has to admit 'Essential COM' was a bit complex
> >
> > COM and DCOM aren't that bad, the performance of DCOM still
> >beats .NET's equivalents hands down and ATL is pretty cool too.
> >It's just that this cool tech is simply lacking easy to use
> tooling ala
> >delphi. I mean: delphi managed to offer C++ speed
> programming and also
> >COM/DCOM creating abilities without the 'don't touch this comments,
> >bubba! we know they're just comments but they're precious material,
> >alright?'-goo.
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
