Before going to Microsoft, I had used COM and OLE via VB, FoxPro, and probably a few other higher-level abstractions. Then I went to Microsoft and worked on OLE DB, using C. O...M...G. CreateObject() suddenly turned into (what seemed like) a 1000 lines of almost-boilerplate. That ADO AddRecord() that was so easy in classic VB? Ugh, if only you knew what was behind that. COM was a clever idea to solve a hard problem, but if one had to work under the covers it was some sausage you were definitely better off not knowing the ingredients of. I mean, COM mostly worked and wasn't bad once you got the hang of it, just like pig snout in your sausage isn't bad for you. It's just kind of unappealing at first.