3 ms·
Apparently the codename for the Pixel (in the chromium os issue tracker, svn, etc) was Link[1], and recently they've added a metallic (i.e. chrome) android stat
by antimatter15 14y ago
Apparently the codename for the Pixel (in the chromium os issue tracker, svn, etc) was Link[1], and recently they've added a metallic (i.e. chrome) android statue (without a corresponding android update) [2]. I might be just over-analyzing things, but there might be some software update in Google I/O signalling a merge between Android and Chrome OS (where the latter is already starting to get features like Google Now on that mobile-convergence pathway like Apple's OS X Lion).
Android has arguably more high-performance, graphics-heavy and touch-enabled apps, and has the toolchains to compile more sophisticated applications (IDEs, etc).
[1]: https://plus.google.com/100132233764003563318/posts/exCKa13F6KZ https://plus.google.com/100132233764003563318/posts/exCKa13F...
[2]: https://plus.google.com/+PaulWilcox/posts/23QtTfiVrtk https://plus.google.com/+PaulWilcox/posts/23QtTfiVrtk
Also, Google has a weird ironic naming paradigm. First is Chrome which is named as such because they want to minimize the browser's chrome (tab bar, menus, buttons, etc.), and now is the Pixel which has a HiDPI display so people kind of forget the pixel. It would probably be a bad idea to call their self-driving car Crash though.
- numbsafari 14y agoI imagine they'll call their self-driving car Driver.
- endtime 14y agoClose - it's "Chauffeur".
- IheartApplesDix 14y agoiirc, it has always been Google's plan to combine Chrome and Android.
- nl 14y agoau contraire Speak to any Googler and you'll hear about the Chrome/Android divide. It's a pretty big issue and possibly Google's biggest weakness.
- GHFigs 14y agoJudging by this interview three years ago, it seems to have crossed the minds of the Chrome OS team, but it would be strong to call it a "plan". JS: And this also gets at another issue. I know that Sergey made some comments that were widely reported about a future merging of Android and Chrome OS, and to me this seems more like a statement of the obvious. In the sense that, once the hardware is full-featured enough to support all the things that you have on Chrome OS, then why do you need something as stripped-down as Android. MP: Yeah, it's unclear. We get a lot of questions like this, and the truth is, I don't know the answer. We're so focused on shipping release one right now, we spend less time than the outside world speculating about what we're going to do next... how will we integrate this with Android... how will we do any number of things like that. -- http://arstechnica.com/business/2010/01/chrome-os-interview-1/2/ http://arstechnica.com/business/2010/01/chrome-os-interview-... The interview as a whole shows where Google's head was at regarding Chrome OS just a week before the iPad was announced, which is itself fascinating.
- nl 14y agoYou really think he's going to say something like: "Yeah, I know that's what Sergey said, but we don't want to merge with Android. We think that the web platform is important and that would be a step backwards"? I think the evidence says it all. Three years later and Chrome & Android are no closer to a merger.