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]
Google made an announcement! It was an OS, in case you haven’t heard. But it was also something else: a long-term, high-risk bet about the future of the internet. Here’s what Google needs to happen for Chrome to make it.
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:
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.
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?
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.
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 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.
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.
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
Here are the first images of the much awaited Google Chrome. Light and spartan, and it seems touch friendly. Enjoy.
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 here.
While the new Google Chrome OS is still at least a year away from being a commercial product, Google’s technology preview this week will be our first opportunity to see Google’s vision for its computing platform.
Google told us that the event, held at its Mountain View headquarters in California, is really designed for developers and third-party partners. However, a select group of journalists and analysts have also been invited to see what Google’s been up to for the last four or five months.
Bookmark this page now and join us on Thursday, November 19 at 10 A.M. Pacific, 1 P.M. Eastern time, for our play-by-play live blog–fresh from the Google Chrome OS event.
10:02 PST: We’re still waiting for the event to start. You’ll find updates after the jump.
[All updates from Mark Hachman]
We’re sitting in a very small, very colorful meeting room where Google’s just minutes of away from giving us a glimpse at Chrome OS and announcing some launch details. Stay tuned!
Update: It’s over! Thanks for hanging out with us, and be sure to check out Google’s videos in our summary post.
Continue reading Live from Google’s Chrome OS project announcement
Live from Google’s Chrome OS project announcement originally appeared on Engadget on Thu, 19 Nov 2009 12:55:00 EST. Please see our terms for use of feeds.
Permalink | | Email this | Comments
Google had a low-key event today to preview Chrome OS, its new operating system based on Linux and the Chrome browser. Things are still pretty early — it’s not even in beta yet, let alone on shipping products — but that’s the first official screen shot right there, and the big features are all roughed out. The entire system is web-based and runs in the Chrome browser — right down to USB drive contents, which show up in a browser tab, and the notepad, which actually creates a Google Docs document. Web apps are launched from a persistent apps panel, which includes Gmail, Facebook, Twitter, and Hulu, among others, and background apps like Google Talk can be minimized to “panels” that dock to the bottom of the screen. Local storage is just used to speed up the system — everything actually lives in the cloud, so all it takes to swap or borrow machines is a login, and you’re good to go. Google also said it’s “very committed” to Flash, and that it’s looking to hardware accelerate whatever code it can — although Google didn’t have a solid answer to give when asked about Silverlight. Overall, Google was upfront in saying that Chrome OS is focused on very clear use cases for people who primarily use the web, and that it’s not trying to do everything: “If you’re a lawyer, editing contracts back and forth, this will not be the right machine for you.”
As far as going to market, Google’s not talking details until the targeted launch at the end of next year, but Chrome OS won’t run on just anything — there’ll be specific reference hardware. For example, Chrome OS won’t work with standard hard drives, just SSDs, but Google is supporting both x86 and ARM CPUs. That also means you won’t be able to just download Chrome OS and go, you’ll have to buy a Chrome OS device approved by Google. Interesting move, for sure — but since the entire OS is totally open-source as of today, we’re sure it’ll be hacked onto all kinds of hardware soon enough. (And for the record, the demo was run on an off-the-shelf Eee PC.) Check Google’s intro videos after the break!
Gallery: Google Chrome OS event
Gallery: Google Chrome OS PR screenshots
Continue reading Google’s Chrome OS revealed — with video!
Google’s Chrome OS revealed — with video! originally appeared on Engadget on Thu, 19 Nov 2009 12:53:00 EST. Please see our terms for use of feeds.
Permalink | | Email this | Comments
We’re liveblogging the Chrome OS reveal today at 10 AM PT, 1PM ET, right here on the Gizmodo Liveblog page. Check back soon to see the OS that Google’s been so coy about the last few months. [Gizmodo Liveblog]
It’s looking increasingly unlikely that Google’s Chrome OS is really launching this week (not that we were really that convinced anyway). What is true, however, is that the company is hosting an event later this week at its Mountain View, CA headquarters to showcase its progress, provide an overview of the platform, and give information on its “launch plans for next year.” Excited? Us, too.
Filed under: Laptops, Software
Google announcing Chrome OS launch plans this Thursday originally appeared on Engadget on Tue, 17 Nov 2009 19:38:00 EST. Please see our terms for use of feeds.
Read | Permalink | Email this | Comments
We’d heard last month that this month was the month that Google would finally launch its highly-anticipated Chrome OS, and now we’ve got a “reliable source” over at TechCrunch asserting that the software is gearing up for launch “within a week.” Granted, we can’t ever be too certain when it comes to a rumor such as this, but if the system really does hit the wilds, we probably won’t see it available for every machine on the face of the planet. The presumed Alpha build will likely only support a select few products that Google engineers have had a chance to specifically work with — possibly something such as an Eee PC netbook, which has generally the same specifications regardless of design or model number. Either way, we’d go ahead and prepare ourselves for something new before the end of November — but don’t let it spoil your holidays should things get pushed back a bit, okay?
[Via SlashGear]
Filed under: Software
Google’s Chrome OS just a week away from launch? originally appeared on Engadget on Fri, 13 Nov 2009 08:27:00 EST. Please see our terms for use of feeds.
Read | Permalink | Email this | Comments
This is site is run by Sascha Endlicher, M.A., during ungodly late night hours. Wanna know more about him? Connect via Social Media by jumping to about.me/sascha.endlicher.
