You scratch our back, and maybe if someone gets around to it...
And only a short time later we see the olive branch in action:
Sam Ruby believes that WSDL is one of the cables of the bootstrap of Web Services. I don't. How will this get resolved? We'll try both ways. If he wants to support services that don't have WSDLs, he'll have to bend. If I want to connect my software to services that require WSDLs, I'll have to. The wild card is other developers. I may drag my heels on WSDL only to find that a developer working in Radio or Frontier solves the problem for us, and same with Sam's environment.
Note this. Sam Ruby'll have to accomodate non-WDSL protocols; on the other hand, if some (unpaid) Radio developer decides to tackle the problem, Dave'll embrace it. See how this is much different from actually agreeing to support WSDL? And there's subtle disrespect in it: If it happens to fall out of the user base somewhere, I'll (maybe) endorse it; otherwise I can't be bothered. This is not working together.