IUnknown vs. System.Object
The dedication of Andrew Troelsen's "COM and .NET Interoperability" reads:
"This book is dedicated to Mary and Wally Troelsen (aka Mom and Dad). Thanks for buying me my first computer (the classic Atari 400) so long ago and for staying awake during my last visit when I explained (in dreadful detail) how System.Object is so much better than IUnknown. I love you both."
Every time I dip my toes into learning .NET, I wind up dismissing it as a hopelessly complex and overengineered POS, but then I encounter something that makes enough of an impression to make me want to reconsider it. This is one of those things... LOL!
"This book is dedicated to Mary and Wally Troelsen (aka Mom and Dad). Thanks for buying me my first computer (the classic Atari 400) so long ago and for staying awake during my last visit when I explained (in dreadful detail) how System.Object is so much better than IUnknown. I love you both."
Every time I dip my toes into learning .NET, I wind up dismissing it as a hopelessly complex and overengineered POS, but then I encounter something that makes enough of an impression to make me want to reconsider it. This is one of those things... LOL!
posted by Coderboi at
10:57 PM
Subscribe to The R5 Blog
1 Comments:
And I'm happy to report that 3 years down the road, I now consider .NET to be the best thing since sliced bread with nothing coming close to it (Java being at a distant 2nd place).
This is thanks in no small part to the existence of languages like IronPython and F# which prove that the .NET CLR is a true multi-language runtime VM, and not a C# only engine.
By
Coderboi, at March 11, 2008
Post a Comment
<< Home