Google unveiled the launch of Chrome OS launching it’s of source code and the software.
Giving a glimpse into its working, Google Vice president of Product Management Sudar Pichai showed how fast Chrome OS boots up, much faster than Microsoft Windows and Apple’s Mac OS X operating systems. Much of the fast boot up process owes to its bare minimum hardware requirement. Google OS devices setup on specific devices called netbooks that will have no hard disks, only solid state disks and would rely on specified Wi-Fi chipsets/adapters for connectivity.
With its launch it has picked up the notices of many big shots literally splitting in two sides on the big debate of will the Google change the way we compute or will Google chrome OS will be the big failure.
The most fundamental feature of the OS giving the insight of how it would be, every application running on the Chrome OS would be web based that is should be able to run in the browser (Google Chrome to be specific). So now our applications don’t have to do whole checking of the list of devices and drivers and loading it to resident memory. Go anywhere, anytime, just log in to your cloud account and have your web applications. User preferences will be synched to a cloud account, so go anywhere anytime, simply log in to your account and get your data and preferences.
Now simple as it seems it has many flaws that have prompted many people to say that it would be a failure, such as the ability of Chrome OS to run only web applications and having little support for offline applications. Thus actually Chrome OS would not be useful in all cases or to all people and in fact many people using it would be having their own full-fledged PC. Now we know from success story of devices such as mobile phones that people want the devices that do it all.
But in spite having its all major backlogs, Google Chrome OS has successfully being able to catch the imagination of people around the globe, holding its promise for the future. Although it may take another 5 to 10 years for the Chrome OS to become conceivably big name in the enterprise computing market but still it has given the developers a glimpse into how we should channelize our efforts in making computers more user friendly and our data more secure. With its source code out many developers must have starting working with applications that will stand compatible with the OS. With greater synchronizations of actions between the developer community and the Google community we can really change the way we compute. Developing applications that can be run from the cloud and then in turn evoke offline processes which can be stored in small but very fast offline memories should solve the conundrum of running the offline applications in the OS. Also that provides opportunities to work towards a coalescent browser that would be a kind of a primary interface to the OS. This can greatly solve our security problems while merging many advantages of a browser, like running multiple applications in multiple tabs; each locked in its own tab so that venerability in one Web application can’t harm the functioning of the other applications and our security update now taking just more than a reboot.
So still being a distant reality, with giant like Microsoft and Apple, still considering it minimal threat, it’s really a great treat to the developer community and the academic world to see the many concepts coming out of research labs to reality and igniting many innovations yet to be unfolded.
Source code available for the developer community at http://src.chromium.org/
Giving a glimpse into its working, Google Vice president of Product Management Sudar Pichai showed how fast Chrome OS boots up, much faster than Microsoft Windows and Apple’s Mac OS X operating systems. Much of the fast boot up process owes to its bare minimum hardware requirement. Google OS devices setup on specific devices called netbooks that will have no hard disks, only solid state disks and would rely on specified Wi-Fi chipsets/adapters for connectivity.
With its launch it has picked up the notices of many big shots literally splitting in two sides on the big debate of will the Google change the way we compute or will Google chrome OS will be the big failure.
The most fundamental feature of the OS giving the insight of how it would be, every application running on the Chrome OS would be web based that is should be able to run in the browser (Google Chrome to be specific). So now our applications don’t have to do whole checking of the list of devices and drivers and loading it to resident memory. Go anywhere, anytime, just log in to your cloud account and have your web applications. User preferences will be synched to a cloud account, so go anywhere anytime, simply log in to your account and get your data and preferences.
Now simple as it seems it has many flaws that have prompted many people to say that it would be a failure, such as the ability of Chrome OS to run only web applications and having little support for offline applications. Thus actually Chrome OS would not be useful in all cases or to all people and in fact many people using it would be having their own full-fledged PC. Now we know from success story of devices such as mobile phones that people want the devices that do it all.
But in spite having its all major backlogs, Google Chrome OS has successfully being able to catch the imagination of people around the globe, holding its promise for the future. Although it may take another 5 to 10 years for the Chrome OS to become conceivably big name in the enterprise computing market but still it has given the developers a glimpse into how we should channelize our efforts in making computers more user friendly and our data more secure. With its source code out many developers must have starting working with applications that will stand compatible with the OS. With greater synchronizations of actions between the developer community and the Google community we can really change the way we compute. Developing applications that can be run from the cloud and then in turn evoke offline processes which can be stored in small but very fast offline memories should solve the conundrum of running the offline applications in the OS. Also that provides opportunities to work towards a coalescent browser that would be a kind of a primary interface to the OS. This can greatly solve our security problems while merging many advantages of a browser, like running multiple applications in multiple tabs; each locked in its own tab so that venerability in one Web application can’t harm the functioning of the other applications and our security update now taking just more than a reboot.
So still being a distant reality, with giant like Microsoft and Apple, still considering it minimal threat, it’s really a great treat to the developer community and the academic world to see the many concepts coming out of research labs to reality and igniting many innovations yet to be unfolded.
Source code available for the developer community at http://src.chromium.org/
No comments:
Post a Comment