3 ms·
My interpretation is that the OS development has been "spiked" to target certain platforms, as a proof and exploration of the tablet form factor. But, as with m
by bobz 16y ago
My interpretation is that the OS development has been "spiked" to target certain platforms, as a proof and exploration of the tablet form factor. But, as with most fast, targeted code pushes, some sacrifices have been made in the generalizablility of the code base. They may want a chance to go back and smooth out their hacks before eager vendors get their hands on it and start building the first at large generation of tablets.
This is just one interpretation, but it's an example of a case where I'd be behind Google's actions.
- cube13 16y agoI agree that this is a good reason why Google doesn't want the code released, but I do not believe that it is a good reason not to release the code. If your Open Source software is good enough to be shipped, the code should be good enough to be released. In this case, I think it's more an issue about how Google is managing expectations with the system. I think it would have made more sense to release a one-off Android branch for the Xoom. In addition, I would have: 1. Made it clear that this code release is a targeted device code release, and will have major issues with other devices. 2. Released a somewhat detailed timeline for when the stable, generalized 3.0 code is expected to be done. The first keeps the homebrew community happy, because they have something they can hack with on the Xoom. It might boost sales marginally, too. The second keeps the tablet manufacturers happy, because they now have a timeline for when Google is going to get a generalized tablet OS out the door.