I've also learned that when you are the lead on a project, you get to define all of the interfaces, and when you aren't, you get to use the interfaces you are given (or, if you prefer, the interfaces that are dictated to you).
You can bitch about it, or you can learn the things you need to do to make it work.
The part that's missing in the above is that people *DO* have a choice as to which API they use. That choice derives from the fact that other companies offer different API's. *I* am paying, *I* am not the one being paid .......
For me one of Tucows key strenghs is it's customer service and very professional and ethical business practices. Thus people like myself use Tucows and accept the tech problems as well as higher fees. However having played "musical registrars" 2 times more than I ever wanted to, so it's in my interest to to try and motivate Tucows to compete more directly with the other APIs and offer one that is platform agnostic -- I say this so that I am assured that Tucows remains strong (read: they continue to grow in market share) but also because I do not have the time you folks obviously do to learn new interfaces and perform "foreign" integration. Of course I only have about 25 years programming experiance, not 30, so you all do have more experiance than me. :p
