He’s a classy one, Mr Brin. Like our own Brian Lam. [CrunchGear, Ryan Block]

[Pirate Bay, gdgt, Techcrunch]

1. First and foremost, do you “get” what Google is trying do do here? Does it make sense? Is it a good idea?

2. Google OS will be available first on netbooks and ONLY on netbooks starting in a year. Do you think netbooks will even be relevant a year from now?

3. Google also mentions that the first generation of the Chrome OS will focus on secondary machines. Do you even have a need for a secondary machine, or is one computer with a traditional OS enough?

4. Google notes that web browsing is the most important function of a computer . Without it, many of us probably wouldn’t use a computer in the first place. So my question is, how much of your time spent on a computer is completely offline?

Just to be clear, I’m not talking about Chrome OS 1.0. You can build that now and (maybe) install it on your netbook, and you should be able to buy it on hardware next year. All that stuff — to borrow a word that Google loves to misuse — is a beta. A test. A trial. A first step toward a larger vision, which Google has been hinting at since they branched out from search: In the future, we will live on the internet. We’ll be able to do all the things we do on computers now, and probably more, while connected to the cloud. And it’ll be great.

Chrome OS is an explicit step towards making this happen, but the version we saw today is just an early, broad step. Google even said so! Despite early talk about how Chrome OS could be a full replacement OS one day, suitable for regular ol’ laptops and desktops, today’s pre-announcement of a version strictly for netbooks included an admission that it would only be intended as a secondary OS. So, what does Google need to see this thing through and make Chrome as capable as the OSes we’re used to using now? Lots:

The Internet Needs to Get Way, Way Faster

And I’m not just talking about higher bandwidth. Broadband connections are pretty quick nowadays, but compared to reading — and especially writing — data to a hard drive, sending bits over the internet is excruciatingly slow. And Chrome OS isn’t even really a true web OS: it’ll slurp the guts of larger web applications like Gmail and Gcal and effectively make them local, meaning that the kinds of tasks that require low latency and fast load times will run tolerably.

That kind of local storage, along with JavaScript technologies like AJAX, is a salve. We need them because communicating with a server for every event in an application would take forever, and make using them miserable. Remember how webmail used to be, before it got all AJAXy? Awful. And it still would be, if not for recent JavaScript advances and local storage.

There’s nothing fundamentally wrong with making web apps local, and Chrome OS will keep doing that forever: it’s the only way Chrome OS can work offline. But that doesn’t cover everything. What about high-bandwidth tasks like photo and video editing? To do it the way they suggest would require constant syncing between local memory and a remote server. These are basic tasks for a computer. Basic tasks that’ll be impossible on Chrome until super low latency, 100mbps+ broadband is not only commonplace, but also wireless and effectively ubiquitous. That’s quite a few years away, even by generous estimates.

Web Apps Will Need To Get Much Better

I’m sure Gmail, Google Reader and Google Calendar will be totally swell in Chrome OS. They’re some of the most feature-complete web apps in the world, and they’re good enough to replace desktop apps for most people. But what about VoIP apps? Torrent clients? Media players? Image editors? Video editors? There are web apps for almost all of these things, but collectively, they amount to a big bag of dick. Trimming videos with YouTube’s tools is nothing like editing them in Final Cut or even iMovie. Cropping a few images in an online photo editor and playing with their contrast is fine, but what about my bloated Sony RAW files? There are still some massive gaps in the web app world, hence Google’s repeated, vague pleas for developers to do better, alright?

Web Standards Will Have To Evolve, Fast

Google wants to replace regular apps with web apps by making web apps more like native apps, in concept and execution. Eventually, the hope is that they could use the new features of HTML5, like local storage, drag and drop, canvas drawing, native animation and location awareness, to have all the powers of a native app. Thing is, HTML5 is just a stepping stone; it’ll take more than a few new HTML tags to pave the way for honestly native-seeming applications.

Google’s obviously got a lot of leverage over standards bodies like the WHATWG and W3C, so they could help move new HTML capabilities along in theory. But even HTML5 is brand new, and very few people are using that. It’ll be at least another generation before developers will be able to code native-equivalent apps in web languages, and that’s assuming that standards development keeps heading in that direction. Which it might not.

Someone’s Going to Have To Solve the UI Problem

Talking about Chrome OS’s interface almost seems like a waste of breath, since your real UI is the internet, which is the very definition of inconsistent. Part of the reason email apps, Twitter apps, IM clients and the like are still so popular is because they offer services that people want in an interface that’s consistent with the rest of their system. Web apps offer no such thing.

Sure, if all you use are Google products, you’re fine: Your life is blue, white, boxy and clean. But what about when you want to jump over to Meebo? Or Aviary? This kind of inconsistency wouldn’t be acceptable in another OS, so it would feel like a compromise here. I suppose you could use tools like Greasemonkey to reformat pages on the client side, but this is hacky and, well, lots of work. We’d need some kind of framework for skins, or something, to make the experience more uniform.

People Will Have To Give Up On Owning Media, an Get Comfortable With Subscription Services

People need their music and videos, and now, most people have collections. That’s sooooooo 2009, am I right? For Chrome OS to work, people are going to have warm up to subscription services and streaming media.

Before you get mad at me, forget about online music stores, and think more about your pay TV company, your ISP or your beloved DVD rental service. These kinds of arrangements are going to have to be extended to all media. Which is possible, but also fraught, since you really won’t own your media.

The Rest of the (Browser) World Has To Be Onboard

During the announcement, Google made the point that the Chrome browser in Chrome OS won’t have any special talents that Chrome elsewhere won’t, and that at present it’s no more able — in terms of what kinds of web apps it can run — than, say, Firefox. Nobody’s going to want to write web apps just for Chrome (that would make them Chrome apps, right?), so it’s vital that other browsers support the same new HTML standards that Chrome need to succeed. Google can go all out supporting the latest, greatest web standards, but unless everyone else does too, nobody — not even Google — is going to write for them.

None of these things are impossible; in fact, most of them sort of feel inevitable, given that they’re all just extrapolations of obvious trends from the last few years. They’re just optimistic, and sit well into the future. Chrome OS can carry out Google’s LET’S ALL LIVE ON THE INTERNET vision when the conditions are right, eventually. But these are long-term bets, measured in years.

That might make sense to a room full of Google engineers. To the rest of us, though? It’s abstract. It’s strange. It seems gimped. It’s largely irrelevant, and it’s not all that exciting. Yet.

You should read our roundup of Everything You Need to Know About Chrome OS. But if you never learned to read (a prospect so full of holes in this circumstance that I won’t begin to address them), watch these clips.

Google Chrome OS UI Concept Video

Google went to great pains to emphasise that today’s event wasn’t a launch — that’ll come a year from now, apparently, with a public beta still well over the horizon. This is all about seeing the OS for the first time; understanding in real terms how it’s different from what’s out there; figuring out why you might actually want to use it. So! Here’s what we knew going in:

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks” and “most of the user experience takes place on the web.” That is, it’s “Google Chrome running within a new windowing system on top of a Linux kernel” with the web as the platform. It runs on x86 processors (like your standard Core 2 Duo) and ARM processors (like inside every mobile smartphone). Underneath lies security architecture that’s completely redesigned to be virus-resistant and easy to update.

Like I said, there were plenty of questions. Onwards:

What It Is

• It’s basically just a browser: meaning that it’ll be based around pre-existing web services like Gmail, Google Docs and so on. There are going to be no conventional applications, just web applications — nothing gets installed, updated or whatever. Seriously.

• It only runs web apps: It’s going to integrate web apps into the operating system deeper than we’ve ever seen before, meaning that a) they’ll seem more like native apps than web apps and b) they’ll be able to tap into local resources more than a typical web app in Firefox, for example. They’re web apps in name, but they’ll have native powers.

• How, exactly?: With HTML 5. This is the next version of HTML, which gives the browser more access to local resources like location info, offline storage — the kinds of things you’d normally associate with native apps.

• Chrome is Chrome: The user’s experience with Chrome OS will basically be synonymous with their experience on Chrome Browser. Technically speaking, Chrome OS is a Linux-based OS, but you won’t be installing Linux binaries like you might on Ubuntu or some other Linux distribution. Any “apps” you have will be used within the browser. Chrome OS is effectively a new version of Chrome, that you can’t leave. There are a few reasons Google’s pushing this, which we’ll get to in a bit.

• And as you’ve probably guessed, it’s super-light. It starts up in a matter of seconds and boots straight into the browser. Likewise, the Chrome browser is apparently very, very optimised for Chrome OS, so it should be faster than we’ve ever seen it.

• It won’t support hard drives, just solid state storage. I mean, hard drives are dying, sure, but this is pretty bold. Hardware support sounds like it’ll be pretty slim, because:

• You’ll have to buy a Chrome OS device: You might be able to hack this thing onto your current machine, but you won’t just be able to install it to replace Windows, or opt for it on your next laptop, for example. You’ll have to buy hardware that Google approved, either component by component, or in a whole package. They’re already working on reference designs.

• For now, it’s for netbooks. It’s not intended for desktops, to the point that Google is saying that the first generation of Chrome hardware will be secondary machines.

How It Looks

• It looks like the Chrome browser — specifically, like the leaked shots we saw before. As in a browser, you have tabs — these have to serve as a taskbar as well. To the left of the tabs, you have a sort of start menu, which opens up a panel full of shortcuts. These are your favourites. These are your apps. (Get used to this weird feeling, btw)

• You can peg smaller windows, like chat windows or music players, to sit above your tabs at all times. This feature looks a lot like the GChat feature in Gmail, which is to say, a box in the corner.

• Along with tabs, it’s got its own version of virtual desktops. This means you can have multiple “windows” of Chrome OS to switch between, each of which is a different set of tabs. Think one desktop for work, one for play, one for porn, etc. It’s a bit like using Spaces on Mac, except only with the browser.

When and How It’s Coming

Google’s staying specifics on the exact release date — it’ll be sometime next year — but the source for the project is published now. That doesn’t mean it’s ready, really, but rather that they’re just planning on developing it in the open from here on out. Expect builds to start showing up online, which’ll probably work wonderfully in a virtual machine app like VirtualBox.

The code is available as part of the Chromium OS (the Chromium/Chrome distinction should be familiar to anyone who’s wrestled with the open source Mac version of Chrome) project, posted here.

Why It Matters

With Chrome OS, Google is taking (or in a way, forcing) the operating system to go totally online. As Google’s freshly designated evangelists are eager to tell you, the browser is already the centre of most people’s computing experience. The idea here is to make the browser powerful enough to render the rest of the operating system, and its native apps, moot.

It’s more pure than a lot of people expected: When Google said that Chrome OS would be centred around the web, I think most people just assumed it to be a lightweight Linux distribution with deep integration for Google web services. It’s not that. It’s a browser.

But it’s a browser that runs different processes for each tab, that will have access to local OS resources, and will to some extent work offline. In other words, it’s not really a browser in the sense that we use the word, and the web apps that we’ll be using won’t be like the ones we’re used to now, either. The idea here, it seems, is to replicate most, if not all, of the functionality in a native OS, while keeping the lightweight, ultra-secure framework of a thin client. In other words, Google’s not asking much of its users in terms of changing how they do stuff; they’re trying to change the way the operating system lets you do those things, transparently.

Think of it this way: Now, the buttons in your taskbar or dock are tabs; your email client runs within your browser, but stores stuff offline just like Mail or Outlook; your documents will still open with a few clicks, but they’ll be stored remotely (and locally only if you choose). It’s all the same stuff, given to you in a different way. [Chrome on Giz]

It looks very similar to what everyone imagined. I’m glad we are moving into single-window, task-oriented environments.

Everything you need to know about Google Chrome OS here.

According to Techcrunch this isn’t is a launch, but a chance to give us a first look at the OS, and for Google to detail the real launch plans (for now, we’re still hanging on the “late 2010″ projection from the initial announcement):

The plan is to give some technical background information as well as show off some demos, we’re told. More notably, they will be giving a “complete overview” of the new OS, which they say will launch next year.

Knowing what Chrome OS will look like is only half the fun anyway — three months after it was announced, we still don’t really know what the hell it is, or how it’s going to work. Soon! [Techcrunch]

Previously, Google had said the release date had been set roughly at H2 of 2010. In their words:

[T]he first netbooks running Google Chrome OS will be available for consumers in the second half of 2010

Of course, that’s when a dedicated product will launch, as in, a netbook from a prominent manufacturer running Chrome OS as sold. But Google did go on to say in the same announcement that that they’d “soon be working with the open source community”, after which Eric Schmidt dropped a few hints that we could see Chrome OS, most likely in beta form “as early as this year”. So, that brings us to the new rumour: TechCrunch has it from a “reliable source” that we’ll see Chrome OS within a week, available as a download. It’ll have limited driver support, meaning Google will only endorse installation on a limited number of computers — mostly netbooks — including a number of Eee PCs.

The obvious question now is what will it look like, though I’d like to remind you that, in all likelihood we’ve been given a pretty good preview: Remember the version of Chrome browser for Chrome OS that leaked for Linux machines a few weeks ago? It had (or has, above) a non-operational Start-style button, a clock embedded in the title bar and a minimalist interface. It’s probably a pretty good indicator as to where Google’s going with this. [TechCrunch]

The only file you can really do anything with is a .deb—that’s a Debian-based Linux installer package—meaning that Debian (and Ubuntu) users can install it with a few clicks. Note: On Ubuntu 9 I got a dependency issue when I tried to install, but it was easy to fix: I just enabled the Universe and Multiverse repositories in Synaptic, and upgraded the library it told me too.

As for the browser itself, it’s not unlike regular Chrome, barring a few telling differences. For one, the clock is on display in the titlebar, as if this browser is going to be the only app you see when using Chrome OS. There’s also a frustratingly enigmatic little Google logo in the top left corner, which looks like a menu. When you click it, it pops up with a prompt to log in with an @google.com email address. Oh well. In any case, downloads are still working from here; feel free to post more mirrors in the comments. [Living in a Google World via Techcrunch]