This happens with all networking. The most well-funded companies oscillate between "trying to get ahead" by hacking in "whatever's next" and selling that to pe

This happens with all networking. The most well-funded companies oscillate between "trying to get ahead" by hacking in "whatever's next" and selling that to people and "just blowing off the spec" because they're not getting paid enough. This is a sedementary process because of whatever business-related adage stops them from rewriting their code. The next awful bit is what happens to the spec itself. We show up in Vegas at the Bluetooth conference in the hottest July on record. No one can share any vision about what this thing is supposed to do, or replace, so everyone just sneezes into the multithousand page specification. The multithousand page specification is actually a paid affair as well, and it's inefficient, confusing, poorly organized, and loooooong, so everyone just ends up building what they think the spec "sounds like." Even better, there's a deadline creeping up, because there's a rumor that Competitor B is pushing out their part of the stack in November, and even if we pay the unbelievable fee to the FCC to get expedited treatment, it's still a 2 month wait, if it's approved -- not to mention legal's checks. ...at least, that's what it looks like to an outsider.