Technknowledge

Dell has released an experimental version of Google's Chrome OS adapted for its own Mini 10v Netbook.

Earlier this month, Google released the source code underlying the Chrome OS browser-based operating system; the first version of the software won't be complete until 2010, when it will become available only when purchased on a computer. But because it is open-source software, others can sample it today if they're willing to build it themselves.
Dell's Mini 10v Netbook

Dell's Mini 10v Netbook
(Credit: Dell)

That's what Doug Anson, a technology strategist for Dell, did.

"I've been doing some tinkering over the last few days working to get our Dell Mini 10v up and running with ChromiumOS. As of late yesterday, I can report success," Anson said on the Direct2Dell community blog.

Anson released the software so it can be loaded onto an 8GB USB flash memory drive. But he offered cautions along with tips to those considering using it. "Use this image at your own risk," he said. "It comes to you totally unsupported and very minimally tested."

Chrome OS uses Linux under the covers, but Google intends for the software to run only browser-based applications. That obviously leaves a lot behind, but Google is among several allies working to gradually improve the Web and browsers as a foundation for programs.

In July, Anson said in a blog post that Dell will evaluate Chrome OS, but he didn't make any commitments to offering a product using the software.

The initial version of Chrome OS is for Netbooks, but Google intends to spread it to higher-end computers after that.
Originally posted at Deep Tech

Word from the LA Times is that Google plans to phase out its Gears plug-in in favor of HTML5 when it comes to augmenting browser abilities. The precise details of its enthusiasm for the plug-in aren't clear yet, but the general trajectory is no surprise.

Google, along with Mozilla, Opera, Apple, and some other allies, has been agitating for features that can make browsers and the Web into a more powerful foundation for Web sites and Web applications. Gears was an early Google effort in this area.

But Gears emerged in 2007--back before Google released a browser of its own, before the World Wide Web Consortium had put its full weight behind HTML5, before HTML5 had gotten the traction it now enjoys as an official standard in the making, and before Microsoft took interest in contributing to that standard.

It's clear things are different now, and HTML5 is solving the same problems Gears set out to fix, and a healthy cooperation is under way for future Web standards work.

Linus Upson, Google's engineering director for the Chrome browser and Chrome OS, confirmed Tuesday that Gears will be supported but isn't an active area of development.

"This isn't an area we've been investing a lot in the last year since we launched Chrome. We're very focused on making HTML5 as successful a standard as possible," Upson said. "Gears applications will run well for the foreseeable future," though, he added.

Browsers including Safari and Chrome are picking up HTML5 versions of Gears features now, he said, and Web applications will follow suit. "I would think over course of next year or so you'll see many more applications take advantage of those abilities," he said.

Perhaps the most notable Gears feature is the ability to store data on a PC so a Web application could work even when disconnected from the network--Gmail and Google Docs being the biggest examples. But that's solved by the local database work in HTML5 that's now arriving in browsers. HTML5 also provides for interfaces with files for better uploading geolocation to let a Web site make use of a person's location.

Various HTML5 elements are just beginning to arrive in Web browsers, and widely used browsers such as Internet Explorer 6 don't have any support at all. But the difficulties of getting people to install Gears or other plug-ins means that built-in browser support probably will reach more people sooner than Gears.

Google has given plenty of signals it's happy to direct Gears energy into HTML5. It proudly demonstrated offline Gmail using HTML5 storage last May at its Google I/O conference, for example. And regarding its O3D and Native Client plug-ins, which accelerate 3D and regular computing processes in a browser, Google developers have argued such technology should be built into the browser, not handled as a separate plug-in.

Google's official position, quoted in the LA Times, is as follows: "We are excited that much of the technology in Gears, including offline support and geolocation APIs, are being incorporated into the HTML5 spec as an open standard supported across browsers, and see that as the logical next step for developers looking to include these features in their Web sites...We're continuing to support Gears so that nothing breaks for sites that use it. But we expect developers to use HTML5 for these features moving forward as it's a standards-based approach that will be available across all browsers."

It was clear from talks at Google I/O that Google sees as a proving ground to try to advance Web technologies and counts it as a victory when Gears technology arrives in HTML5. Now the only real question in my mind is whether the pace of HTML5 development in the standards world will satisfy Google.

Upson said Google will continue adding features into Chrome and its Chrome OS, even if that means deviating from standards at times.

"Ideally for all these things (such as Native Client and O3D) we'd like to get them into standards," Upson said. "At the end of the day, we can't control the pace of the Internet Explorer developer team at Microsoft (or developer teams) at Mozilla and Apple. We all have a shared incentive to not fragment the Web, but there always will be seams that aren't smooth."

Updated at 5:14 p.m. PST with comment from Google.
Originally posted at Deep Tech

MOUNTAIN VIEW, Calif.--Google's dual-pronged operating-system strategy will likely produce a single OS down the road, according to Google co-founder Sergey Brin.

Many Google observers were puzzled when the company announced plans for Chrome OS in July, coming amid growing acceptance of the company's Android operating-system project as a smartphone and Netbook OS. After all, why design an open-source operating system with the goal of reinventing the personal computing experience when you're currently developing another open-source operating system with the goal of reinventing the mobile computing experience?

Google executives, including CEO Eric Schmidt, have downplayed the conflict ever since, asking for time to let the projects evolve. And a few days after Chrome OS was revealed, Android chief Andy Rubin said device makers "need different technology for different products," explaining that Android has a lot of unique code that makes it suitable for use in a phone and Chrome has unique benefits of its own.

But Brin, speaking informally to reporters after the company's Chrome OS presentation on Thursday, said "Android and Chrome will likely converge over time," citing among other things the common Linux and Webkit code base present in both projects.

It's not clear when Google thinks it might want to merge the projects, but it seems to be eyeing a future in which the smartphones currently served by Android meld into the Netbooks Google has in mind for Chrome OS. Of course, Brin's vision might not necessarily be shared by all members of the Google management team.

"As Sundar [Pichai, Google's vice president of product management] said in his presentation, we're reaching a perfect storm of converging trends where computers are behaving more like mobile devices, and phones are behaving more like small computers," Google said in a statement in response to questions about how and when the two projects would merge. "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."

This also allows Google to pick and choose the best ideas to emerge from each project, setting up a bit of friendly internal competition to develop new operating-system technologies. The main difference is that while Android is a shipping product, Chrome OS is still very much in the research stage, with devices not expected until late 2010.

It's way too early to know how that pending convergence will affect development for the different operating systems, as it seems pretty clear Google is spending most of its time at the moment building out each one separately.

But Brin--no idle bystander--believes at some point, Google will emerge with one next-generation operating system.
Originally posted at Relevant Results