Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Abel Avram on Jul 08, 2009
Google has announced they are working a new operating system called Google Chrome OS. Based on a Linux kernel with a new windowing system, the new OS is targeted at netbooks first and will be open sourced and free.
After dominating Microsoft in the search field, after entering the mobile market with Android, Google is entering right in the heart of Microsoft’s business: the operating system. Google is following their vision: an entirely online world where all data and applications are on cloudy servers, and the user needs only a browser to access all that. Google has a browser, Chrome, but they want an operating system fearing Microsoft will eventually catch up with them and ultimately will marginalize them having control of the most dominant OS.
They actually do not want to recreate a new full-blown OS, but rather take a Linux kernel, and create a new minimal windowing system on top of it. The main and probably the only application running on it will be the browser, Chrome. The other applications are online, accessed through the browser. The idea is to offer Chrome a support that is not controlled by someone else and practically reiterates the war of the 90’s when Netscape wanted to cover the desktop with their browser, making Windows irrelevant.
Google will open source the code of the Chrome OS later this year, and invites the community to join their efforts when that happens. They are also in talks with several manufactures to produce netbooks by the second half of 2010, but they are not going to stop with netbooks. They want to take it to laptops and desktops. While Android is also on netbooks, they say the two products will actually complement each other, Android being targeted at mobile devices. Chrome OS will run both on x86 and ARM processors.
Developers will be able to work as usual using their web platform of choice. They just do not target the desktop, but will create online applications as they have already done so.
Google wants to build the new OS for:
Speed, simplicity and security… We're designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don't have to deal with viruses, malware and security updates. It should just work.
Google clearly takes aim at Microsoft by saying:
People want to get to their email instantly, without wasting time waiting for their computers to boot and browsers to start up. They want their computers to always run as fast as when they first bought them. They want their data to be accessible to them wherever they are and not have to worry about losing their computer or forgetting to back up files. Even more importantly, they don't want to spend hours configuring their computers to work with every new piece of hardware, or have to worry about constant software updates.
Some of the companies Google is working with to make this happen are Acer, Adobe, ASUS, Freescale, Hewlett-Packard, Lenovo, Qualcomm, Texas Instruments, and Toshiba. The most interesting name in the list is Adobe, a software company. This indicates Adobe AIR will get good support on the new OS and probably will continue to have a good support of Flash inside the browser, Chrome. It is interesting to see what will Google do regarding Silverlight which is currently supported by Chrome 2.0.
A new page of history begins. It is difficult to say what the outcome will be. Google will certainly drive some of the market, but Microsoft will also react. We need to wait and see their reaction. Their first move is suggested by the research conducted for a much more secure browser, code name Gazelle. And Google’s path to success is not so straightforward. Online applications are not as mature and fast as desktop ones. There are still networking issues remaining. There is a very large number of people using desktop applications, and that is not going to change any time soon, but we are living in a fast changing world.
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Agile Development: A Manager's Roadmap for Success
Regaining control of the data centre
Architectures Behind Facebook, Skype, Sky.com, Bwin, League of Legends @ QConLondon
If Google makes Chrome OS boot as fast as a TV, I think it will be the best choice in the "web and cloud computing epoch".
I would not hesitate to pay for a cheap license if they succeed at making it fast and simple. Jakob Nielsen was right, the art of simplicity is the key to get happy users. Google understood that from the beginning.
I am using almost every Google Web applications and for the simple usage that I make it is just perfect. It might not be as fast as desktop applications for people having slow connections but the beauty of it is there is no risk in loosing our data, it is free and it is accessible from anywhere!
It's doomed to failure. It's the same brain-dead thinking that Larry Ellison and Scott McNealy had in the mid-90s.
Or will it be "A TV takes as long to turn on as a computer?" More and more, it seems we're getting away from instant on with electronics. Just look at the growth in time it takes to start from VCR to DVD to Blu-Ray.
Big question... how well will it handle those folks who have spotty net coverage? Will the Gears (or whatever they use) implementation be up to the task?
Also, HTML is increasingly showing its age (and it was decrepit at least 10 years ago). We really need a common application markup that takes into account what the dev world wants/needs to do, not a document markup perverted into an application markup.
Operating System that is free and has a google stamp will fly to certain level. But given that their own Browser has such a paltry share and the fact they will be giving the world "Yet Another Distro", I have to say "Good Luck!!!"
"Yet Another Distro", yes, so we can choose Ubuntu, SUSE, Fedora... or Chrome OS. But I don't think it's simple as that. We all know what Google did with Android. Android is just "Yet Another Distro" for mobile devices, but it created a buzz on marketplace.
I think they will reuse Android to build Chrome OS.Android being targeted at mobile devices. Chrome OS will run both on x86 and ARM processors
What about JavaFX? I think it has a very good future in the Chrome OS.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
7 comments
Watch Thread Reply