|
|
|
|
|
by orangecat
5540 days ago
|
|
If the code is good enough to go in production devices, why isn't it good enough to be released to the public? It's quite easy to create a code base that mostly works well, but whose structure and organization is utterly unsuitable for a public release. This is especially true when you have a marketing-driven deadline (e.g. "ship before the iPad 2") and have to take shortcuts. |
|
The quote from Savoia and Copeland in the article seems to be saying that Google won't release the code until the product sees market in order to maintain their competitive advantage. That's one thing. But when they continue to sit on the code when the product is out, that's another thing entirely.