Tag Archives: Chrome

Thoughts on Google Chrome OS

I’ve resisted writing anything on the recently-announced Google Chrome OS, for a number of reasons… the most significant one being that so far, we don’t know a huge amount about it. This hasn’t stopped reams of opinion being written or spoken about it anywhere else though, so a week on from the announcement, I thought I’d lay down a few opinions of my own.

First of all, I always felt that the Chrome browser itself kind of pointed towards an operating system, since the engineers were clearly thinking in terms that you’d usually associate with an OS – ideas like the threading model immediately made me think of the domain of the operating system. The “Google OS” has been one of those rumours that has consistently failed to die.

So what do we know? We know that Google Chrome OS will be based on Linux and will be largely open source, and that the initial target constituency will be the netbook market but that it has ambitions to the desktop. We know that it will have a new windowing system (bye bye X). We hear that Google has been courting various netbook manufacturers, and we know that it should be out sometime in 2010.

On the threat to the desktop

Scott Bourne was saying on MacBreak Weekly this week that he felt this meant it would be no real threat to Mac OS X, and I guess the ensuing discussion really sparked the majority of this post. Scott based his assertion on a straw poll of people who he’d asked “OS X or Chrome?” (a: OS X) for laptops, and “Chrome or Windows Mobile?” (a: Chrome) for PDAs. I just think that’s an impossible discussion right now. So far it’s vapourware. We don’t know what Google Chrome OS will look like and we don’t know what features it will have. It’s pointless to try to compare it to existing operating systems at this stage.

The other reason the MacBreak Weekly crew decided that Chrome OS wouldn’t be a threat was that it would initially be limited to netbooks but “will it actually be able to make the step up to the desktop?”. This is an interesting discussion, as it assumes that the granddaddy / holy grail of machines is the desktop computer. But… wait a minute. Haven’t Apple spent the past two years convincing the whole mobile market that they have to have fully-capable computing platforms on their handheld devices? Isn’t the netbook market exploding? Aren’t laptops outselling desktops? Aren’t computers and televisions converging via set-top boxes and streaming media? People want computing power and access wherever they are, in a form factor that fits. I think the suggestion that the desktop is still “where its at” is deeply, deeply flawed – the desktop is dying, and has been for a long time. The desktop is a place where people occasionally anchor themselves, but the rest of the time they are moving around and taking their platform with them.

So is it a threat? On netbooks, in my opinion, yes – probably to both Linux and Windows. As for Apple, they aren’t going to be keen to let anyone run another OS on their hardware, and they’re not currently in the netbook market, so it probably is not a big deal right now. Windows XP still seems to be an OS of choice on many netbooks, but Microsoft probably will finally kill that with Windows 7. There are too many Linux distributions around (Linpus, Moblin, Ubuntu) vying for a slice of that market. The Google brand, combined with an experience that is genuinely pleasant, could take chunks out of both sides of that market. From there, who knows… but if it is Linux-based, we already know that that scales from big to small machines, so there are plenty of places it could go. I personally think it will be interesting to see where they choose to go with the user interface, and this is the area that will determine the future.

On the cloud

I think the idea that Chrome OS could be a lightweight system with the majority of content hosted in the cloud is particularly interesting. How secure are we all feeling this week about the safety of the cloud? In the light of the Twitter hack, I imagine that people are rethinking the security of the public cloud, anyway. Paired with a secure behind-the-firewall private cloud, a lightweight OS like this makes a lot of sense. That’s not to say I don’t like the flexibility that cloud/web-based services offer me – I use many of them, including things like Google Docs. Of course, you need a network connection for it to be effective, and it’s true that bandwidth is becoming pervasive, although if you take a look at 3G coverage for various UK mobile operators (hint, look at the PDF and the maps *per operator*, not the overall coverage map), you might want to rethink your dependence on that, too.

On the image

Will Google be able to get away with labelling Chrome OS “beta” to start off with? I think that in order to get people to use it, beyond the Google brand name, it will have to be really good, polished, and / or flashy and convincing enough as an initial experience for people to base their computing lives on it. I think it will probably have to have had more testing than many of the existing Google cloud web products.

Final thought

Right now, all we can really say is: “well, this is interesting”. We can speculate, but frankly, I don’t think we know enough to say anything more. That’s all I’m sayin’.

Advertisements

On the Chrome bandwagon

Well Twitter and the interwebs sparked up with discussion of Google’s new browser, Chrome, late last night (UK time) and I thought I’d add some ill-formed thoughts of my own. Don’t expect reasoned, complete analysis at this point: the morning coffee is sitting beside me unsipped…

First thing to say is that I enjoyed the web comic that leaked out a day before the formal announcement, although I did wonder at some of the logic at the time.

  • Chrome installed very smoothly on Vista. For a beta, it’s remarkably stable and well-featured. It has been no real secret that Google have been at least tinkering with browser technology for a while, but they’ve made a very credible entry to the space by coming along with something so (relatively) complete and solid as a first release.
  • I didn’t quite get the reasoning behind the inversion of current UI paradigms with the tabs along the top of the window. I’ll be interested to see how this looks across the major OS platforms. Phil mentions that it’s probably easier when each tab represents a separate process, and Phani points out that it lets them associate the address bar and tools with a tab rather than the window. I guess I’m more used to a platform-native look-and-feel now.
  • Some of the touches in chome-bad-httpsthe UI are quite nice – sites with insecure SSL certificates appear with a crossed-out line through the https, and in common with Firefox 3 it initially warns with a big red page when the site is not trusted.
  • It seems fast, but I typically browse with a lot of tabs open in Firefox so I could just be “used” to a slower browsing experience brought on by bad habits.
  • On that note, the concept that a “bad tab” won’t kill my browser really, really appeals to me. The design of this feature leaves me wondering whether we are going in another technology loop (processes good, threads bad) but I’m willing to be convinced.
  • I like the idea of the start page with thumbnails of favourite pages. I’ll be the other browsers adopt that soon.
  • I like the idea of “application shortcuts” which can go straight onto the desktop. It makes sense. Lots of applications are webapps now.
  • Flash “just works”. Java does not.
  • On the subject of plugins… I’ve come to depend on a lot of the plugins that I can get for Firefox. Given the heritage of the Chrome development team, and the model that the comic describes for isolating plugins / scoping them to a tab, I assume that it will be possible to extend Chrome… but the user-visible extension points are currently limited (no menu bar, no status bar) so it will be interesting to see how they approach this and what the take-up is likely to be.
  • The developer tools that are built-in are very impressive… nice source viewer, element inspector, and the “task manager” with “stats for nerds” gives an interesting glimpse into the way the browser and task isolation is working.
  • RSS feeds don’t appear to display. I half-expected an RSS link to whisk me off to Google Reader – I have no doubt that all my base WILL belong to Google here. Maybe that’s a “todo” feature.
  • Another technical thought – are images in Chrome rendered with colour profiles? I assume so since it uses WebKit, but I’m not sure.

I’ve been saying to people for a while now that Apple has been worth watching… using WebKit as the basis of Safari, Dashboard widgets for OS X, and the iPhone. With this (re)use of the same techology by Google, I’m intrigued to see where all of this will take the browser. With Google’s brand recognition and reach, this has the potential to be a very disruptive move.

Update: WOAH, major licensing issues. And Mark Cathcart brings some interesting perspectives, too. For now, I’m removing Chrome.

Update: as Mark and Justin note below, the EULA has been fixed. Chrome gets a reprieve and can come back to my system, for experimentation purposes at least.