4 ms·
The problem that I have with this comment (and many of the stories like the one linked) is the simple fact that, although this is obviously a blatant attempt to
by SweltertheCook 16y ago
The problem that I have with this comment (and many of the stories like the one linked) is the simple fact that, although this is obviously a blatant attempt to re-write history via corporate PR (something that Google does just as often as any huge company), it really is true (in an overall sense-- Google certainly is attempting to avoid a future where the iPhone is dominant. Whether or not you think that's "draconian"... well, really, stop right there. How many HN posts are there about various App Store debacles? Censorship? If it isn't "draconian", it is certainly less than "free"). Google is doing something to challenge Apple here, and they are doing it in all the right ways.
I have a Droid, and a good friend has an iPhone. There are times when I really wish I had his phone instead of my Droid, but there are also a lot of times he wished he had an Android device. Like it or not, Apple has competition, and that's forcing them to innovate rather than letting developers do it for them via the App store. Tethering, built in MiFi-like capability-- these are things that Apple's good friends in the App store can't do for them, and Google is right to go after them. Likewise, although it is very likely I'll try to turn off/disable Flash support if my Droid is ever updated to 2.2 (or if I ever root it and go with Cyanogen, etc), it is a weakness of the iPhone, iPad, and going after Apple where it will actually hurt is more than fair game.
Again, I don't think giving Google a pass here (or worshipping at their temple) is a good idea per se. But I do think that a lot of the criticisms leveled at Google for this comment have less to do with Google's real sin-- PR manipulation-- and more to do with the fact that a great deal of Apple supporters are a bit chagrined that Google is doing so well against the iPhone.
Just look at Gruber. I mean, I love the guy-- read his site every day, as I think it is some of the best Apple analysis out there-- but as Google I/O has gone on, his normally cogent commentary has degenerated into what basically amounts to one-line (or one-paragraph) sniping over Google's attempts to challenge Apple. As if Apple somehow has the right to complete 100% dominance of the consumer smartphone market.
Again, like Google or not, I think its hard to argue that Android isn't a serious challenger to the iPhone (and soon the iPad, if Android-lovers have their way). And its hard to argue that this is ultimately good for consumers-- certainly much, much better than an Apple-run world where political satire is banned from our phones simply because it might ruffle a few feathers or distract from Steve Job's vision of the "perfect" App Store.
- commandar 16y ago>Just look at Gruber. I mean, I love the guy-- read his site every day, as I think it is some of the best Apple analysis out there-- but as Google I/O has gone on, his normally cogent commentary has degenerated into what basically amounts to one-line (or one-paragraph) sniping over Google's attempts to challenge Apple. As if Apple somehow has the right to complete 100% dominance of the consumer smartphone market. The thing about all that to me is the way he's been almost intentionally been obtuse about some things in order to snark about them. He's been conflating the difference between private system APIs and undocumented application APIs on Android lately, even after acknowledging a response from Tim Bray about the whole thing a couple of weeks ago. Andy Rubin made a comment a while back about how Google doesn't use private APIs in Android, and Gruber's just been chomping at the bit to somehow use this as an example of Google's hypocrisy. So when Google says something like "You really shouldn't be doing things like accessing the SMS app's internal undocumented methods because there's no guarantee they'll be there on all distributions of Android" [because the SMS app is just another application and not a core system component], Gruber jumps up and down pointing at it as an example of how Google lied about not using private APIs. Maybe it's just me, but telling developers that they should stick to public system level APIs rather than try to muck around with the internals of applications that aren't a part of the core system hardly sounds like some tacit admission that Google is really using private APIs on the sly to me. Google's entire point about private APIs is that you can do anything you see a Google app do using the public system APIs because that's what the Google apps are using in the first place, rather than relying on hidden systems calls that aren't made available to normal developers. It's frustrating, because when Gruber is right, his analysis is usually a great read (plus I love Markdown). But lately he's been fanboying so hard on this and a couple of other things that it's gotten painful for me to follow him.
- commandar 16y agoIf anyone's interested, here's one of the DF posts about this: http://daringfireball.net/linked/2010/05/06/curious http://daringfireball.net/linked/2010/05/06/curious Tim Bray's reply: http://www.tbray.org/ongoing/When/201x/2010/05/06/Private-APIs http://www.tbray.org/ongoing/When/201x/2010/05/06/Private-AP...