4 ms·

Is Chrome OS a stepping stone from Android as a 'stretched-out' OS, or more in the way of Android trying transitioning bigger screen formats, such as: http://w

Is Chrome OS a stepping stone from Android as a 'stretched-out' OS, or more in the way of Android trying transitioning bigger screen formats, such as: http://www.motorola.com/Consumers/US-EN/Consumer-Product-and-Services/DROID-Bionic-Accessories-page/DROID-Bionic-Accessories http://www.motorola.com/Consumers/US-EN/Consumer-Product-and... I know they're obvious differences, but I'm focusing in the similarities...does anyone see my point? Would love to know other's opinions.

drivebyacct2 14y ago
I don't know, but why Google and Asus don't release a Transformer that dual boots Android and Chrome OS is beyond me. Yes, Flash already has ARM ports working anyway.
- trotsky 14y ago
  They are working on an arm port for an unnamed device but it seems like it's still under heavy development. One reason you likely won't see something like the transformer running chromeos is their upstream first policy, which suggests that they won't ship chrome on devices that don't have their driver base included in the base linux kernel. There are exceptions, but I get the feeling they aren't interested in core drivers like graphics being one of them.
  - drivebyacct2 14y ago
    Ugh. That makes an unfortunate amount of sense, I hadn't even thought through the embedded device drivers problem. Extremely frustrating across devices and OSes. :[
jallmann 14y ago
To hazard a guess: the higher-ups at Google think (know?) that the future lies in the open web. Android is a stopgap to compete in the current mobile environment, but I'm hoping ChromeOS displaces Android entirely in the next 3-5 years. WebOS started down that path, and Mozilla is really doing it right with B2G. I think Google realizes the same. This transition can't happen suddenly. Google may also be waiting for the rest of the mom-and-pop web to catch up with the capabilities of native apps (via WebRTC, WebGL, etc) without having to depend so much on extensions, NaCl plugins and the like. At that point, ChromeOS will "just work" for rich applications alongside the rest of the web, which neatly sidesteps any fragmentation issues.

drivebyacct2 14y ago

I don't know, but why Google and Asus don't release a Transformer that dual boots Android and Chrome OS is beyond me. Yes, Flash already has ARM ports working anyway.

trotsky 14y ago
They are working on an arm port for an unnamed device but it seems like it's still under heavy development. One reason you likely won't see something like the transformer running chromeos is their upstream first policy, which suggests that they won't ship chrome on devices that don't have their driver base included in the base linux kernel. There are exceptions, but I get the feeling they aren't interested in core drivers like graphics being one of them.
- drivebyacct2 14y ago
  Ugh. That makes an unfortunate amount of sense, I hadn't even thought through the embedded device drivers problem. Extremely frustrating across devices and OSes. :[

jallmann 14y ago

To hazard a guess: the higher-ups at Google think (know?) that the future lies in the open web. Android is a stopgap to compete in the current mobile environment, but I'm hoping ChromeOS displaces Android entirely in the next 3-5 years. WebOS started down that path, and Mozilla is really doing it right with B2G. I think Google realizes the same. This transition can't happen suddenly. Google may also be waiting for the rest of the mom-and-pop web to catch up with the capabilities of native apps (via WebRTC, WebGL, etc) without having to depend so much on extensions, NaCl plugins and the like. At that point, ChromeOS will "just work" for rich applications alongside the rest of the web, which neatly sidesteps any fragmentation issues.