Teo en Ming, the ChromiumOS64 project lead, says of the download:

"The original Chromium OS project does not support 64-bit platforms. This is because the majority of the netbooks in the market are based on Intel Atom processors, which are mostly 32-bit."

With Chrome OS launching properly at the tail-end of 2010, we've got a full year to wait before we see anything more solid become available. And even then, it'll only be available on Google-branded devices, with Acer hoping to launch the first official netbook running it.

Let us know how you get on with the 64-bit Chromium browser below. [ChromiumOS64 via TechRadar]

Acer has been developing a Chrome-based netbook since mid-2009, and its Chairman, JT Wang, has told DigiTimes, he wants it to be the first netbook out there when Chrome OS is released in the second half of 2010. [DigiTimes]

Wi-Fi is a little wonky, but otherwise, it should be totally fine. Just plug the flash drive with the image into the 10v, and you should be able to boot right into Chrome OS. The usual pre-beta caveats of stuff breaking, etc., apply, of course. [Direct Download, Dell via Liliputing via Download Squad]

Ultimately, Ubuntu Netbook Remix 9.10 did the best, and openSUSE 11.2 also did well. But Chrome OS performance was far from spectacular. That shouldn't be a huge surprise, though. It's not slated to ship for like a year, and its performance should pickup as builds continue. The main surprise looks to be Moblin 2.1's comparatively slower speed, despite Intel's efforts to optimize it for netbooks. It looks pretty, though.

All distros were tested with default configurations/packages, except for Chrome OS. They "needed to remount the root file-system in a read-write mode and add in the standard Ubuntu Karmic package repositories for which Google's operating system is based."

The Phoronix test suite included H.264 video playback, OpenArena, LZMA and 7-Zip file compression, IOzone, PostMark, WAV to OGG audio and H.264 video encoding. Full test results at: [Phoronix via Slashdot]

Google, asked how on earth this slow-motion, oddly-planned scenario would play out, gives mixed responses. The official PR line, when asked about the merger:

[W]e're reaching a perfect storm of converging trends where computers are behaving more like mobile devices, and phones are behaving more like small computers. Having two open source operating systems from Google provides both users and device manufacturers with more choice and helps contribute a wealth of new code to the open source community.

There, perfect: acknowledge that your boss's sentiment is true, but deny any specific plans. But what about when CNET asks Schmidt directly? Observe:

The future will unfold as it does.

There it is! When these guys are talking about Chrome and Android merging, they're not talking about any kind of roadmap, they're just speaking in obvious, unusually long-term truisms, like they've been doing an awful lot lately: Two Linux-based operating systems from one company are bound to develop similarities; eventually, our computing usage will be totally centered around the web; in a decade, our notebooks and cellphones will probably be one device; the future is awesome; etcetera.

This Zen futurism is charming and all, but Chrome OS and Android aren't uncontrollable entities—they don't need to be crudely estimated, or attributed some kind of autonomy, especially by the people that make them. Specifically, they need to be planned. [CNET via Download Squad via Engadget]

He's a classy one, Mr. Brin. Like our own Brian Lam.

(Note: I actually do find Sergey's choice of phone and footies to be slightly more interesting than anything else Google announced today.) [CrunchGear, Ryan Block]

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 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 for much in the first place. So my question is, how much of your time spend 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 should be able to buy on hardware next year. All that stuff is, 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 preannouncement 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 commonplace, and not only commonplace, but 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 Rhapsody and Napster, and think more about your cable company, your wireless company, or your beloved Netflix. Those work, and 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 needs 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 in 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.

Google Chrome OS UI Concept Video

Google went to great pains to emphasize 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 a 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; etc. 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 preexisting 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. More on that here.

• 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 boot straight into the browser. Likewise, the Chrome browser is apparently very, very optimized 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 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 favorites. These are your apps. (Get used to this weird feeling, btw. That Google whole point here.

• 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, it's 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, on for porn, etc etc 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 code 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 center 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 centered around the web, I think most people just assumed it would 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, 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 now tabs; your email client now 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.
Update: you can download it here. [Chrome on Giz]

According to Techcrunch this isn't really a launch, but rathe a chance to give us a first look at the OS, and for Google to detail their actual launch plans (we've been sitting tight with 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 set 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 rumor: 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 nonoperational Start-style button, a clock embedded in the title bar, and a minimalist interface, and it's probably a pretty good indicator as to where Google's going with this. [TechCrunch]

The only file you can really do anything is is a .deb—that's a Debian-based Linux installer package—meaning that Debian (and Ubuntu) users can install it with a few clicks. On Ubuntu 9 I got a dependency issue when I tried to install, but is 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]

This is all total speculation, but a writer on ReadWriteWeb suggests that it may mean Google intends to lock down Chrome OS to only use Google software, in order to keep things simpler and easier. After all, it's tough to use a single sign-in (SSO) cookie if you don't control the software being signed in to. However, I don't think this is likely—all of Google's software (Gmail, Picasa, Chrome, Blogspot, Earth, etc etc etc) uses a single sign-in, and I think that's all the phrase "login manager" implies. But the question remains: In a browser-based OS, what happens if you want to change browsers? We'll have to wait for more information before we know. [ReadWriteWeb via Electronista]

First, the rumor is that Chrome OS will have a new windowing system. Basically, a windowing system where there are no windows, and all apps run always in full screen mode. Second, who in hell uses CRT monitors at Google or anywhere else? That just seems weird.

Still, it's polished. I like the simplicity, and the always present search field. Makes me wish that Mac OS X Spotlight was connected to the internet at all times. [Mashable]

Before we dive in, it's worth talking about exactly what we're going for here. What "theory of Chrome" are we planning to adhere to? Or perhaps more to the point, what the hell is Chrome? From Google:

"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.

From our own Matt Buchanan:

If I had to guess, I'd say Chrome OS is somewhere in between an entirely browser-based OS and a generic Linux distro, though leaning toward the former.

In other words, Chrome, as we understand it, and as Google describes it, is a Linux OS that lives on the web, depending almost entirely on Google's suite of services, which are served through a special, Google-designed interface. We have no way of knowing what this mysterious window manager, menu system or desktop environment will look like, so we can't replicate that. The web half of Chrome OS, though, is already in place, and ready for us to clumsily unify. So, we'll make our own stripped-down operating system. Here's how:

Get Yourself Some Linux
Before embarking on this goofy afternoon software project, we need a launchpad. Specifically: Linux. You could go with almost any distro and accomplish the same effect, but this guide will be focused on a distribution called Xubuntu. Why Xubuntu? Because it strike a perfect balance between being extremely compatible and easy to install—on both counts, it really is—and, since it's essentially just a version of the uber-popular Ubuntu Linux distro with a stripped-down, super-fast desktop environment called XFCE, it's quick, and lightweight. Anyway, head over the the Xubuntu website and start downloading. (Go with 9.04 the latest stable version.)

There are a few ways to handle this. If you're planning to install Xubuntu on a netbook—Chrome's first and most natural target—you're probably going to need to create a bootable flash drive. Ubuntu provides some fairly fantastic instructions for doing this on Windows, Linux and Mac OS X. If you're trying to do this on a regular laptop or desktop, or you have an external optical drive, you're going to want to burn your downloaded ISO to a CD and install from there. Alternately, you can order a free install disc from Xubuntu. Lastly, if you're like me, and you just want to test this out in a free virtual machine like VirtualBox, all you need to do is boot a new system from your downloaded ISO. At any rate:

During the installation, you'll be prompted with a number of options. Make sure to check the "Log In Automatically" radio box—it'll make your boot-to-browser experience a little smoother later on.

Once you've finished the installation—this should take no more than a half-hour, really—you'll find yourself with a pretty, fresh new Xubuntu desktop. It's really nice! But now, it's time to start replacing it.

Choose Your Browser
So obviously, you'll need a browser. This is the center of the Chrome experience—the window through which you'll access Google's suite of services, and which you may never leave. It needs to have support for all the web's various technologies, be it Google Gears—a plugin that lets Google services store data offline, so they can load faster and function offline—or Flash, which makes the internet significantly less boring. Chrome OS will ship with Google's Chrome browser, obviously, but the Linux port is a little sickly right now. Gears, for example, doesn't really work right now, and Flash, though technically available, crashes constantly. But if you really want to stay as Googly as possible on this project, you can get Chrome for Linux (Chromium, it's called) by adding these lines to the "Sources" list in a program called Synaptic, which manages Linux applications through one, unified interface, and is accessible in your System menu.

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu jaunty main

You can find out how to enable Flash here. Pro tip: don't bother with this.

Counterintuitively, the best way to get the Google experience on Linux is with Firefox. Xubuntu comes with Firefox, but you're going to need to spruce it up a little. Ok, a lot.

Make That Browser Work
First, you'll need Flash. Open Synaptic—mentioned above—from your Applications>System menu, and search for an item called "Flashplugin," (it's Flash Player 10) or navigate to the item as shown in the below screenshot.
Click "Apply" and let the installer run its course. Now, Firefox should support sites like YouTube, Pandora, et al.

Now, you'll need Google Gears. This is a simple Firefox extension, which you can download here. This'll help make living online feel a little less like, you know, living online—think offline archived email. Most of Google services can use Gears, so you'll want to go through each site's settings page to enable as many "Gears" or "Offline Access" options as possible. Docs and Mail are where you'll see the biggest differences, since Gears turns them from web services into full-fledged offline apps, transparently. Pretty amazing stuff, and one of the few features we know will be in Chrome OS.

Next, you'll need the Google Toolbar. This, in absence of whatever interface voodoo Google is sitting on, will serve as a sort of constant dashboard for Google services in the meantime. Along with providing shortcuts and notifiers for services like Gmail and Googel Caldner, it's got a few little tricks that'll make your browser feel more like a proper OS. For example: in the Google Toolbar preferences, you can check options that enable both automatic Gmail-ing or Mailto: links, and automatic opening of many document formats in Google Docs. You'll want to enable these, since we're trying to create the illusion that the rest of the OS doesn't exist, which an errant OpenOffice window or email client could shatter, God forbid.

Lastly, grab yourself a copy of an extension called Speed Dial, which will give you a Grid-based homepage of favorites which you can populate with all the core Google Services you're going to need—Gmail, Reader, Google Docs, Google News, etc—and which will be the first thing you see when you open your browser, and eventually, your OS. Set the initial configuration as I have on the left.

And if you're really into this idea for some reason, you can download a Firefox skin that looks like Google Chrome here.

Getting Rid of Everything Else
Now that you've got everything you need to live wholly within Google's ecosystem, a la Chrome OS, you need to remove everything else—that means excess browser clutter, system menus, and pretty much anything else that stands between you and your Google suite.

The first step will be to strip out your Firefox interface, which is probably looking a bit bloated by now. I've posted my small-screened solution below, which you can replicate by dragging and dropping icons however you please in Firefox's View>Toolbars>Customize menu. The above configuration lets you totally remove the Bookmarks and Navigation bars, which saves a good deal of space. Feel free to play with this for a while—you might find that you don't need one input box or the other, or that you can get away with much less of an interface than I have.

After grinding down Firefox's interface to an acceptable size, you'll need to go to work on your desktop. Before you can kill all the menu bars and shortcuts you don't need, you'll need to make sure Firefox automatically loads at startup, so you're basically booting into the browser. You can do this by navigating to Applications>Settings>Session and Startup, and adding a new startup item with the values seen below. (The last one if the only one you can't change—it's the one that launches Firefox).

Now, it's time to murder everything else. Right-click on either the top or bottom system panels—the Start Menu-like things on the top and bottom of your desktop—and click "Customize Panel." From here, you can remove the top panel, and set the bottom panel to "autohide." Once you're done, restart. Upon boot-up, this is about all you should see:
Welcome to Chrome! Kind of!

See What You Think
As I said before, what you've just slapped together here is not Chrome, and Google's final product will probably look nothing like this, superficially. But this little web-savvy Frankenstein OS does, I think, capture something of Google long-term vision, in which everything we store, use and experience on our computer is based online—preferably on their servers—and native applications are nothing more than a small, necessary evil. This experiment is less about guessing the specifics of Chrome OSes interface, under-the-hood workings or usage model (three things which I'm fairly sure this fails at) than it is about deciding whether or not the the idea of Chrome OS suits you, and how you use your computer. That, at least, you can get a taste of. So, how do you like it?

So that's about it! Please add in your experiences in the comments-your feedback is a huge benefit to our Saturday guides. Good luck with your OS impersonation, and have a great weekend!

That's not to say that Schmidt left over a tussle in the App Store, or even the FCC's recent investigation into Apple's handling of Google Voice apps, but these little shitstorms could've been a reminder that, as much as Apple and Google have worked together over the years, they are competitors in all kinds of markets, from online services to cellphones to browsers to, soon, OSes. On this, the brief press release doesn't mince words:

Unfortunately, as Google enters more of Apple's core businesses, with Android and now Chrome OS, Eric's effectiveness as an Apple Board member will be significantly diminished, since he will have to recuse himself from even larger portions of our meetings due to potential conflicts of interest.

Therefore, we have mutually decided that now is the right time for Eric to resign his position on Apple's Board

It's hard to tell if this "mutual decision" was kind of thing where Schmidt just saw the big picture and said "Hey y'all, it's been real," or if the rest of the board told him to pack his bags, but either way, it seems like the inevitable is happening, and Google's entering its next stage of evolution as a tech compay, full of flamewars and fanboys, taunting blog posts and constant controversy. Pick your sides; this should be fun.

Gundotra reiterated a lot of what we already know. Google believes the future of the computers lies in the browser, with apps coded according to web standards and data existing in the cloud. However, what stood out as interesting was that Gundotra, who isn't directly part of the Android team, referenced all this in the same breath as the rapid evolution of mobile browsers and mobile data plans. While he never explicitly referenced Chrome OS, it seemed evident that the upcoming, browser-based platform was in his head as he spoke.

After all, part of the point of Chrome OS is that it scales—from netbooks to desktops, so why not down to phones? And if the future is in web apps, why wouldn't Google move its web app OS down to phones once the ubiquitous connectivity is there? In Google's worldview, native apps are already just about archaic—just a necessary evil in Android's case.

He also spoke on how browsers and web standards are advancing so quick, that web apps will be more powerful than people realize: "Steve Jobs had it right when he said build for the web. But timing was an issue." And it looks like for Google, the time is now. [Chrome OS]