5 ms·
I think you mean "not very open", as in not community built, or some other type of extreme openness like that (open <-> close is a scale, it's not black or whit
by mtgx 14y ago
I think you mean "not very open", as in not community built, or some other type of extreme openness like that (open <-> close is a scale, it's not black or white). But I'd argue that while Android should remain open source (you can use the source once it's ready), it should be even more "closed", in the sense that Google needs to have a lot more control over what the manufacturers/their partners can do with Android.
Why? Because it's the only way to ensure a cohesive "ecosystem" that helps not only Google and their Android users, but also the manufacturers themselves in the long run. After all, if everyone had their own little fork of Android, and there wouldn't be an "ecosystem" anymore, that wouldn't benefit them at all, as these days it's all about "platform wars", and splitting one big platform into 10 different ones would actually hurt the manufacturers, not help them.
This is why I think Google needs to "close" Android even more i.e. standardize it a lot more, and even demand from manufacturers to release their drivers. It would be awesome if they told them to release open source drivers, but even closed source ones would be useful, because if everyone did this, Android could actually (eventually) work like Windows.
You would be able to install "Android" on any 2-3 year old smartphone or tablet. But that's only if the manufacturers would be forced to release those drivers and maintain the support for that amount of time. And that's only possible if the Android ecosystem becomes a little tigher/more closed, or "less open" (as in manufacturers can't do whatever they want, and they must obey a set of rules for the well being of the ecosystem).
- xentronium 14y agoThey are already exerting control over what their vendors can and can't do. See asus aliyun debacle.
- staplesowns 14y agoAcer
- xentronium 14y agoI should proofread my comments better, acer indeed.
- fluidcruft 14y agoThat's a pretty extreme example and really more of a Google vs carrier battle than a Google vs Asus battle. Aliyun was trying to establish a Play competitor and lock Google out--you can't expect Google to play along. Since Honeycomb Google's been pretty strong relative to manufacturers. The biggest pre-Honeycomb threat was Motorola that was thrashing to cut Google out and get back in control (Skyhook, BlurOS) and... well you can see how the constellations happened to align there. What Google was threatening to yank wasn't access to Android, but access to the Platform Development Kit and possibly unannounced Nexus projects--i.e. access to the pre-Open Source drops. Someone like Amazon can pull that off because they don't care, but certainly Asus doesn't have the muscle. Asus was free to choose Aliyun or Google, it's not Asus's fault that Aliyun isn't as valuable.
- xentronium 14y ago> but access to the Platform Development Kit and possibly unannounced Nexus projects--i.e. access to the pre-Open Source drops As far as I understand, it also meant access to all google services for all acer (not asus, my mistake) smartphones. So it's an ultimatum after all.
- kgarten 14y agoYes, I was pointing at the community aspect of open-source. Just to get some source dumps after a while does not mean "open-source" to me. Seems people at Hacker News see this differently. Yet, I agree with your comments, in general. Why not split it like they did for Chrome (suggestion in the comment below).
- blinkingled 14y ago>Yes, I was pointing at the community aspect of open-source There is a good reason for that. Show me one "community driven" open source project successful in the scale that Android is. Think about it, think about the other community driven SmartPhone OS projects and why they failed. What trade offs Google makes with Android are very fair and necessary - once they get the kernel bits in Korg it will only get better.