http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/ Engadget Comments for http://www.engadget.com/media/feedlogo.gif http://www.engadget.com en-us Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only. Blogsmith http://www.blogsmith.com/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:39PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:39PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:41PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Chrome runs on very limited hardware. Android runs on totally different hardware. Android is good at multitasking, running java, making phone calls, taking pictures, blue tooth, etc. Its ok at javascript.

Chrome OS is good at javascript.]]>Nov 24th 2009 7:02PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 9:31PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
A browser is not a substitute for an integrated application environment, period. Google needs to realize that EVERYTHING does not belong in Javascript. Other languages exist for a reason - they're better at certain things.]]>Nov 25th 2009 2:37AMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Android and ChromeOS are both Linux, they both run on x86 and ARM. As they have the same kernel, if there is a driver for one, it'll work on the other.

The only differences:
ChromeOS has the lightest-possible-weight windowing system, only meant to run Chrome. Android has Dalvik.

Takeaway:
ChromeOS says "go web developers!" Android by its existence says "Make me apps!" and owners think "I want some apps!" Is it stupid that ChromeOS doesn't have Dalvik? Yes. Third parties will put it in, but it's still stupid that Google won't.]]>Nov 25th 2009 2:54PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:41PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
you might actually be the 1st 1st to be Highest Ranked.]]>Nov 24th 2009 6:41PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:42PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:42PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:50PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Boot it on a netbook and youll see its future. It takes sub 5 seconds to logon. ]]>Nov 24th 2009 7:08PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Then there is also the use of netbooks in the classroom. A cheap $200 netbook with Chrome OS would be much easier to afford than a laptop for every student. Not to mention it would be much lighter and could be carried around with their books.

Aside from education, there are actually some people that do nothing more on their computer than check their email. Chrome OS would be perfect for them since they don't have to worry about breaking it or getting a virus.

And taking it even further (and this is probably pushing it), Google has 3 other projects that could change how people think about Chrome OS, assuming they take off.

Google Gears - http://gears.google.com/
O3D - http://code.google.com/apis/o3d/
NativeClient - http://code.google.com/p/nativeclient/

Gears is already built in to chrome and provides offline access to Gmail and what not. O3D is an API to provide 3D graphics in the web browser, you can download the plugin in chrome and try it out. NativeClient actually lets the website run native code on the user's computer, while keeping the sandboxed security model. ]]>Nov 24th 2009 9:27PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Unfortunately, Google has never been known for coming up with mind-blowing interfaces. What they HAVE done, however, is make the cloud-based computing platform that much more interesting by diving into it.]]>Nov 24th 2009 10:37PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Chrome OS + ARM CPU + 2GB flash drive < $150, plus huge power savings, no need for anti-virus and internet security apps, no cost for the OS itself, and virtually no need to maintain or update the OS.

Add that sub-$150 combination to your average x86 notebook, and you have a secondary mode that can double your battery life exactly when you want it: when you need to conserve battery life while surfing the internet. The bigger the power requirement differential between the x86 CPU and the ARM CPU, the greater the relative difference between battery life running the x86 CPU and the ARM CPU. So, take a top of the line gaming notebook PC with a quad-core CPU, dual HDDs, and a discrete GPU; the Chrome OS "module" takes the 1.5-hour battery life to a 20-plus-hour battery life. (The numbers are only guesstimates.) If Chrome boots and shuts down around the same time it takes to get network access and start up the browser on your main OS, then it's obviously useful in a number of real world cases.]]>Nov 25th 2009 9:01AMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 27th 2009 11:17PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:44PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
That allows cablecoms, satellitecoms, broadcasters, etc to program to one unified system for on-demand apps, EPG, etc.]]>Nov 25th 2009 6:52AMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
(and I agree with all your comments of douchyness and ranked down into oblivion)]]>Nov 24th 2009 6:46PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:46PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:47PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 25th 2009 1:35PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
]]>Nov 24th 2009 6:49PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:52PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
What we have is an O/S designed for mobiles and one for netbooks. Not exactly a conflict.

The argument is that Chrome could take apps away from android.... but android has the same browser. And Safari hasn't damaged the iPhones app store to any significant degree (and you can make some really nice web apps that look like real apps)]]>Nov 24th 2009 6:49PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Phones != smartbooks.

Argument destroyed in two words and 1 symbol.]]>Nov 24th 2009 6:51PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 6:58PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 7:00PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Android OS & Chrome OS exchanging information similar to Cloud.

Flip open Android/Chrome device same information is up, same data is accessible.

You can quickly realize how many lay-persons would appreciate simplification of their browsing and computer experience.

But what about: my office programs?? etc??

as the programing evolves so will Google Docs, and related programing. Eventually imagine a Chrome OS App store with direct linking to a Android OS app store.

All of a sudden, the issue with owning a computer makes sense.

we go to a grocery store for organized collections of things we may need in our day. We go to a convenience store for similar items in a swifter more direct version. Equate that to Chrome and Android, and now you may get an idea of the convergence. ]]>Nov 24th 2009 6:55PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Certainly but the though is incomplete - You can't blame the developers only especially when google is on their back. If you will look at the release of chrome OS this week, thye hype is really crazy. One could say, that the Google fever has been a part of your lives

What's the buzz about Chrome OS? detail review : http://bit.ly/google-chrome-os-best-or-worst-judge-it

Now I can't see why the article is Mixing Android With Chrome? Hmm, Chromes are for netbook and Android are for smartphones, am I correct?]]>Nov 24th 2009 7:02PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
If Google can knock off interoperability between it doesn't matter if it's Chrome or Android--that would be a huge win.]]>Nov 24th 2009 7:05PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/

I am just using 1080p h264 as an example, not saying that it is sufficient, just that if javascript could handle that without tricks and native code, then I couldmore readily see that type of convergence being possible.]]>Nov 24th 2009 7:12PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/That might include carriers actually realizing the word "unlimited" already has a meaning and that it is not 5GB.
But seriously - the bandwidth is a question and more-so on portable systems so a web-centric vs local-app fight is not a fight at all.
It is apples and oranges...
Or in this case googles and other different googles.]]>Nov 24th 2009 7:15PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
In the recent E. Schmidt's (Google CEO) interview, he responded to this Chrome-Android-conflict issue by reverting to the well-used cop-out of "we'll let the community decide our course." And while it is indeed a well-worn refrain, he does have a point, given that these are both o-s projects, and partners as well as tech hobbyists will have a large influence--larger than with Microsoft or Apple's initiatives, certainly--on how to slice and splice them.

At first glance, Goog's efforts do seem disjointed. One would expect a large corp to have better coordination. But better coordination doesn't necessarily mean better product. The o-s paradigm of "throw it out and let people pick" has produced many gems, and Goog's crowdsourcing approach certainly deserves the benefit of the doubt, especially this early in the product's life cycle.

On Chrome: I think it would be ideal for the tablet form-factor (no hard KB). Imagine a $100-150 ARM-based 10" tablet w/ 6-10 hr battery life, that is used primarily as a web browser and e-book reader, and secondly to play some music & video. That's the smartphones' main appeal (aside from PIM/contact functions), and it'd be the same for tablets. No hard keyboard is a plus, since it differentiates the tablet's use from a netbook's.

Microsoft failed with its first tablet and is retrying w/ Courier. Apple is reportedly giving it a go. Amazon/B&N are dinking around the edge w/ Kindle/Nook. Chrome may well be Goog's entry to its own tablet.]]>Nov 24th 2009 7:38PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
Ow. That sentence - like much of the article - is just painful to read. Bad author, no cookie.]]>Nov 24th 2009 7:39PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 7:43PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 8:04PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 8:06PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 8:06PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 8:25PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 8:34PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
i don't think this competition within google is necessarily a bad thing. they are implementing two very different strategies, perhaps one will win out in the end, perhaps both will find success. the teams will undoubtedly learn from each other. i don't see how you can argue against innovation and experimentation.

my personal prediction is that android will eventually folded into the chrome project. google is a web company and their goal is to keep people on the web as much as possible. where chrome is a radical change from what people are used to android is a fairly traditional phone OS, it is easy to attract former winmo or iphone or palm users. once they've got a good market share with android, they can eventually adapt the android platform to be more and more like chrome.]]>Nov 24th 2009 8:58PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 9:03PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 9:31PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 11:11PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 24th 2009 11:15PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
The Android platform is largely developed by mobile phone manufacturers like Motorola, HTC, Sony Ericsson, Samsung, etc. The Chrome OS does nothing to deter them from handset makers from developing Android.

Moreover, Chrome OS as a platform is going to be largely locked down. It won't allow the use of binaries, and instead will rely on HTML5, AJAX, Flash, to develop applications and utilities. ]]>Nov 24th 2009 11:41PMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/Nov 25th 2009 3:20AMhttp://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/http://www.engadget.com/2009/11/24/switched-on-chromes-shine-could-blind-android/
The advantage these "HTML5" local apps have over "smartphone-specific" local apps is that they can be "installed" on ANY device running ANY OS (smartphone, netbook, tablet, eReader, desktop, etc.), so long as the device utilizes a modern, HTML5 browser.]]>Nov 25th 2009 4:18AM