> Al what you are saying is, there is a market out there for this > particular "car" to come with a spoiler on the back of it. a large > portion of your current users WANT this feature, a large portion of > people who are looking at cars in the market SPECIFICALLY are looking > for this feature, yet you as a manufacturer simply refuse to put the > wing on the back.
Except that, in your analogy, Google doesn't make cars. HTC, Motorola, Samsung, et. al. make cars. Google makes drivetrains, which have nothing to do with spoilers, except to those who think car parts are car parts. For example, there are versions of the HTC Magic that will ship with Exchange support. AFAIK, this required minimal involvement, if any, from the core Android team. http://bit.ly/DzmLq Moreover, AFAIK, Exchange connectors require licensing technology from Microsoft, most likely under terms that do not work with open source. Hence, just as device manufacturers work with PacketVideo to add WMA/WMV support, device manufacturers will work with third parties to integrate other Microsoft-licensed technologies like Exchange. http://bit.ly/16wYSF If you have evidence to suggest that it is possible to license Exchange connector technology in a fashion that is compatible with open source, please post it. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
