Hasta La Gadget!

Sometimes you have to take a step down to step up. That’s what Google should’ve done with its open source PC operating system Chrome OS, which the corporation demonstrated Thursday.

Instead, Google is positioning Chrome OS against Microsoft with a lightweight OS shipping with netbooks next year. Chrome OS will function as a modified browser, enabling netbooks to handle everyday computing with web-based applications. That’s right: No native software, just the web.

The philosophy behind Chrome OS is extreme: Go the web way, all the way. It’s a “paradigm shift to make the web synonymous with the computer,” as Mashable’s Ben Parr puts it. But it’s an idealistic vision that could take several years to actualize, given the currently limited state of wireless connectivity and web-based applications. Google is aware of that, and the company is merely massaging us with this radical idea of a web-only computing experience by suggesting we try it on netbooks first.

Looking ahead, the company said it plans to share Chrome OS with more-powerful devices, including notebooks and desktops. But we doubt consumers will show much interest in a Chrome OS netbook the way Google is currently packaging it.

With Chrome OS, the search giant is pushing an OS that enables us to do less — even less than already low-powered netbooks can do. Web apps can’t let us process Microsoft Word documents, sync our iTunes libraries, or edit photos with Photoshop, for example. Thanks to their crampy keyboards and small screens, netbooks aren’t ideal for productivity apps such as Photoshop or Microsoft Word — but you’d be surprised at the different uses for netbooks that made them last year’s hit product category. Watch what happens when Google offers an OS that doesn’t at least provide the option of using the aforementioned apps.

Of course, as Google’s pitch goes, there are web alternatives to everything. Cloud storage for backups, internet-streaming music and video services, and the Google Docs web suite for all your spreadsheet or word-processing needs. The list goes on.

The idea is such: Give up the computing experience you’ve grown accustomed to for over a decade. Come live in Google’s browser.

Why would anyone wish to do that today, tomorrow or even next year when the OS ships?

Michael Gartenberg, a tech analyst at Interpret, sums up the state of computer use today better than anyone else: “What we’ve seen is most users are looking for a combination of the two: rich applications on my desktop, and the apps where I want to be connected.”

“This idea that I’m somehow going to do away with rich app architectures and do everything through the browser is an old argument, and it’s never taken root,” he added.

The benefits of Chrome OS don’t seem to outweigh everything Google’s modified browser will do away with. The pluses: Tight security, thanks to Google’s careful monitoring for malware in Chrome OS apps; saving the money you’d spend on an external hard-disk drive thanks to cloud storage; ultimately, being able to “stop worrying about your computer,” as Google said in a promotional video shown at its Thursday event.

Stop worrying about our computers? We’re worried about you, Google. T-Mobile Sidekick customers should especially be disenchanted with the cloud. Microsoft, T-Mobile and Danger hosted the data of all of T-Mobile’s Sidekick users in the cloud, and recently the server crashed, losing everything.

Nobody’s perfect, so it’s conceivable that the same thing could happen with Chrome OS. After all, Google’s Gmail service crashed in February and again in September this year. While no data was lost, it did cause hours of angst for people who had grown dependent on the mail service.

And then there’s money. Aside from losing access to the native apps we’ve paid for on our PC, it’s certainly imaginable that using Chrome OS could get expensive in general. If we wished to put an always-connected, web-app-only computer to good use, we’d need to purchase a data plan from a carrier. This could come in the form of an EVDO card or a smartphone tethering plan — in other words, a monthly bill. Google said Chrome OS will have caching features, so you won’t need internet access to do everything, but caching won’t provide the same offline experience as a full native application.

(Of course, our wireless problems could be solved if we could find an open Wi-Fi connection just anywhere we go. But unless you live in Mountain View, California, where Google provides free Wi-Fi, ubiquitous, free hotspots are not part of your reality.)

With all that said, there’s a ton of potential here for Chrome OS to be vastly appealing, and I’m keeping an open mind. To succeed with Chrome OS, Google should take a step down. To start, Google should modify Chrome OS into a “mini OS” of sorts that can live alongside another OS, such as Windows, on a netbook.

For comparison, Phoenix Technologies offers a mini OS called HyperSpace, which some netbooks are already shipping with. HyperSpace runs parallel to Windows as an instant-on environment, allowing netbooks to perform internet-centric functions without actually booting into Windows. Functions include multimedia players, browsers, internet telephony, e-mail and IM.

Sounds a lot like what Chrome OS is going to be, doesn’t it? That’s because it’s almost the same idea, only Phoenix Technologies is a lesser-known company (which developed the BIOS that boots many Windows computers today, by the way) and is taking a humbler approach — offering HyperSpace as an optional, complementary (but not complimentary) OS rather than a full-blown substitute for Windows. It’s an approach that could lead to greater results if embraced by an incredibly powerful brand like Google.

By offering Chrome OS as a free, downloadable mini OS that runs parallel to a full one, Google can still continue to expand its presence onto hardware — without having to sell the OS with netbooks. Consumers could still try out the benefits of Chrome OS and cloud computing when it’s convenient for them. Then, if users wished to boot into their primary OS to back up their data or do document processing with Microsoft Word, for example, they could — a hybrid, more feature-rich experience.

Unfortunately, not everything we want is on the web just yet. That’s not going to radically change in one year, and not even Google can change that.

See Also:

• Google Chrome OS: Ditch Your Hard Drives, the Future Is the Web
• Five Things Google’s Chrome OS Will Do for Your Netbook
• Google Announces PC Operating System to Compete with Windows …
• You Predict the Winner of OS Wars: Chrome, Windows, Linux, OS X?
• Google FAQ Reveals Chrome OS Hardware Partners

Photo: Melanie Phung/Flickr

Itching for some Chrome OS? Well, we all are, but you might be a bit disappointed at the fact that while Google has open-sourced its progress on the OS so far, the version that is currently available for download seems eons behind what Google showed off at its event yesterday. Still, if you just have to see it for yourself, the good news is that it’s a total breeze to get a virtual machine running. We used a VMWare image that was packaged up by the kind folks at gdgt, and set it up with VMWare Fusion running on a recent model MacBook Pro. Your mileage may vary depending on your particular setup (there’s also an image available for the free, cross-platform VirtualBox software), but the principles should remain the same. Check it out on video after the break.

Continue reading How-to: run Chrome OS as a virtual machine

How-to: run Chrome OS as a virtual machine originally appeared on Engadget on Fri, 20 Nov 2009 14:15:00 EST. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Wow, that was fast. Google Chrome OS was only unveiled today, and it’s already compiled as a VMWare image, ready for download via torrents and gdgt. Techcrunch also has a tutorial for setting it up. [Pirate Bay, gdgt, Techcrunch]

There’s obviously something seriously wrong with me, since the idea of a feature-stripped OS that over-relies on a web browser at the expense of more powerful single-purpose apps has delightful shivers running up my spine. In fact, in a fleeting moment of ill-advised adulation, I was considering buying a netbook with solid state storage so that I’d be all prepped to hack this pre-release version of Chrome OS onto it and web-app to my heart’s content. The real issue is that at the end of the day I know I’m always (well, for the next few years at least) going to be too reliant on “heavyweight” desktop applications like audio, video and image editors to really cut the cord and stuff my whole life into the cloud. But the chimes of freedom flashing in Chrome OS are too great to ignore, and I think there’s plenty going on here that could be very beneficial to a “real” desktop OS.

Continue reading Editorial: Chrome OS is what I want, but not what I need

Editorial: Chrome OS is what I want, but not what I need originally appeared on Engadget on Thu, 19 Nov 2009 16:20:00 EST. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Until today, Google’s Chrome OS has been little more than a wordy concept. Now, finally, we truly know what it is, what it looks like, and how it works. Here’s the breakdown:

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]