Sunday, March 31, 2002

Is .NET COM Interop fundamentally flawed?. [Sam Gentile's Radio Weblog] I hope this starts a healthy discussion. I haven’t worked with COM interop yet. But I want to hear about all of the issues. COM interop is something that every .NET programmer will need to understand. We need guidance regarding the real costs of COM interop. Should we continue our current COM development? Should we use COM interop to leverage our COM investments? Should we move our COM code to .NET? There are no simple answers of course, there never are. But thanks to the .NET pioneers the rest of us won’t have to work as hard. Keep up the good work everyone…    ... This is a cool site: http://www.old-computers.com. How many have you touched? [deem] ... This was the first computer I ever saw ! It meant the beginning of my madness... [Oliver] Me too Oliver...but mine was the US version. This was next: http://www.old-computers.com/museum/computer.asp?c=98    ... Check out the movie or picture viewer showing 3,304 picutres taken each mile on a drive across the US. [found via MetaFilter] [deem] I can’t believe I haven’t seen this before. I woke up this morning at 5 thinking about XML Serialization. I did a little DOTNET list spelunking. Then I saw Mike’s post. I watched the entire movie. Then I played with the picture viewer for a while. It brings back a lot of memories. Between family trips as a kid and work trips as an adult I’ve seen almost every place on that route.    ...

© Copyright 2002 Matt Griffith. Last update: 05/24/2002; 10:04:55 PM.