The main problem with versioning the API is that many of the hardware partners cannot easily update their API interface and this leads to a 'legacy' approach to

The main problem with versioning the API is that many of the hardware partners cannot easily update their API interface and this leads to a 'legacy' approach to maintaining the API. Having had a background in enterprise software, I can tell you how frustrating this can be. If the NetFlix API had versions, you can quickly see how this would proliferate out of control. Devices from each class (assuming the versioning was done on a time release basis) would probably need to be supported for about 10 years (the expected lifetime of the device). This would mean NetFlix would end up supporting over a dozen versions just to keep its hardware partners happy. Another solution would be to insist that all hardware accessing the API must be capable of being flash updated. This would allow NetFlix to insist on supporting each API version for only a limited amount of time (sufficient for the hardware to be updated just like any other software service). NetFlix basically has the choice of dealing with the complexity internally or forcing the ecosystem to suck up the pain. Their choice will be driven more by business concerns (who needs who more in the relationship, what are each parties' options) than technical (what can we do given how much money we are willing to throw at the problem).