A random thought popped into my mind after thinking about this previous post on CoreOS's plans for rocket:

A similar parallel happened with iOS when Jobs refused to support Flash on iPhones back in the day. He believed that by introducing another layer of APIs for multimedia on the web, they would be depreciating the value of the native APIs that iOS had already made / were planning to add. There was a lot of discussion at the time about how flash would only end up using some fraction of Apple's APIs and always be lagging behind support for new ones. So developers using flash would always have poorer UX than those using Xcode / Cocoa / Objective-C (And now Swift).

With Rocket / Docker, any new features CoreOS may want in their containers would have to be integrated into Docker (Controlled by Docker, Inc.), rather than in a manner controllable by their own team. The same way that Rocket is meant to prevent CoreOS becoming a commodity, Apple didn't want their APIs / system becoming an underlying layer for Adobe to develop upon. It just happened in the opposite order this time.

A thought...