Well, maybe this was a case of the PR machine being too far out front of the technical reality. But when I see a launch video and a list of companies using OpenSocial, and TechCrunch reports on it so positively, I figure it's ready for some action, not still under development.
>>Obviously > there will be differences between containers, but there will be a common > base that is supported on all containers, some parts that are supported by > most containers, and some extensions that are supported by only a single / > couple of containers. This scares me. Browser wars, anyone? Without strong top-down control, containers will go off and extend functionality in new ways for their users, just as IE did. And web devs know how wonderfully that worked out for us. How many times do we ask ourselves why code works in all browsers except IE? And how many IE-specific fixes are there out there? It's just surprising that a company would propose an inclusive, 'make life easier for devs' product, and then not maintain the quality control necessary to realize that goal. Plus, it's in the container's long term interests to abide to a common spec. A common spec is easier to develop to, which means more devs will try it, which means containers will get more apps. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial API Definition" 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/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
