The 5 best, and 5 worst, features of Google Chrome OPERATING-SYSTEM

On the plus side, Google has promised that Chrome OS devices will have the following five goodies:

1 )  Speedy boot-up, as fast as three-seconds. A Chrome OS device will not store any applications on the device itself. Nada, none, zippo, says Pichai. Likewise, it will include only the hardware, right down to the component level, that Google has approved in the hardware reference specification. The only applications it is going to use are those that can be run from the cloud in an internet browser, the Chrome browser, to be specific. One of the major reasons for this is to speed up shoe time. With no local applications and limited hardware, the device doesn't need to run through long checklist looking for devices and drivers, loading programs into resident memory etc. It should turn on like a television, says Pichai. Flip a change and the within three seconds browser should be available, showing the most recent browser windows.

2)  Security automatically. The part of the operating system needed to operate the device will reside in a read-only section of memory. The rest of the operating system is integrated with the Chrome browser and, like the browser, security updates require nothing more than a reboot. Silver OS can run multiple Web applications in multiple tabs and each one is locked down from all others, so a vulnerability in one Net iphone app can't lead to exposure in another. User data stored on the device, which is little, is encrypted. User data is limited to items such as user tastes. All other data will be stored in the cloud. User preferences will also be synched to a cloud account, so like any thin client. should you lose the device, you will merely record in from another one and your data and tastes should be there.

3)  Support for both x86 and ARM architectures. Google promises that it will be writing native code for both popular netbook computer CPUs.

4) The application menu. As new Net applications come online tweaked for Chrome OS, Steel OS will showcase them on a long term tab it now calls the program menu. This will help users find new applications. Developers with new programs will find this a simpler method to showcase them, too. Any Web software that runs in a standards compliant browser should work on a Chrome OS device. But Chrome OPERATING-SYSTEM is focused on supporting new protocols such as HTML CODE 5, which, among other improvements, natively supports rich media.

5)  A amazing way to aid Microsoft Business office. If you ask a Google executive any question involving Microsoft, you'll listen to the cliche answer -- that they company thinks only of users and not of its recognized competitors. But in one of the giggle-inducing occasions of Thursday's demo, Pichai, showed how Chrome OPERATING SYSTEM would handle Office documents -- via Microsoft Workplace Live, the free Web application version of Office offered to Windows Live users. In the event that an user clicks on an. xls document, Stainless- launches Excel via the browser in Office Live. "Microsoft launched a killer software for Chrome OPERATING-SYSTEM... and is working very hard to do this, inch he quipped.

But Chrome OS also has a number of downsides:

1) It truly is considered a companion device. Google doesn't claim that this Web-only device is useful in every cases or to all people and fact thinks that most people who buy it will also own a full-blown PC. As the product will be too big to become a mobile phone, people will also still need one of those. The big lesson of the iPhone's success is that individuals want devices that do it all -- and preferably with 1000s of downloadable applications, too. Chrome OS devices will neither do it ing nor allow applications to be downloaded to the client.

2) Vague support for working offline. The device is built for connectivity. The only way to work with programs and data offline is if the application creator buids some sort of system into the app, supported by Chrome OS, says Pichai.. Google was hazy as to how this would be done, but presumably through Google Armor and weapon upgrades. Gears is the technique utilized by Google Apps for off-line access. Applications have to specifically support it and since of yet, few do.

3) Nope, Android applications won't work on Stainless- OS devices. Android programs must be downloaded to the product so they are automatically not compatible with Chrome OS.

4) Zero options for choosing another browser. Chrome is built into Chrome OS. In the event you want Firefox, or (gasp! ) Internet Explorer, you can't have it. On the other hand Google points out that Chrome OS is open up source. This means that Mozilla or Microsoft or others can grab the Chrome OS code, develop their own Chrome OS os, integrate an alternate browser, and convince their own set of OEM manufacturers to build compatible devices. How likely is that?

5) Uncertainty about plug-ins and other methods of modification. As mentioned above, google says it will eventually lean seriously on HTML 5 for Chrome OS, which, among other attributes, uses a standardized rich media format. This makes it unnecessary to download proprietary internet browser plug ins such as Adobe Flash and Microsoft Silverlight. Of course, few Web sites today use HTML 5. Interestingly, Google and bing executives absolutely promised that Chrome OS would support Flash when devices delivered nonetheless they were evasive when asked about Silvelight, saying only that they would share more info about how the OS would deal with plugins at some point in the future. Users won't be able to install binaries, so this doesn't just leave Silverlight out in the dark. All plug-ins, widgets, applets and other poular methods for modification are stuck under in the same vague cloud.