Google Chrome OS

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Google Chrome OS
Google Chrome icon and wordmark (2011).svg
Chrome OS 21.0.1172 Aura Dev.png
Google Chrome OS (21.0.1172.0) displaying the app drawer and Chrome browser.
Company / developer Google Inc.
Programmed in C, C++
OS family Linux
Working state Preinstalled on specific hardware (Chromebooks, Chromeboxes)
Update method Rolling release
Package manager Portage
Supported platforms x86, ARM
Kernel type Monolithic: Linux kernel[1]
Default user interface Graphical interface based on the Google Chrome browser
License Google Chrome OS Terms of Service[2]

Google Chrome OS is a Linux-based operating system designed by Google to work exclusively with web applications. Google announced the operating system on July 7, 2009 and made it an open source project, called Chromium OS, in November 2009.[3][4]

Unlike Chromium OS, which can be compiled from the downloaded source code, Chrome OS only ships on specific hardware from Google's manufacturing partners.[5] The user interface takes a minimalist approach, resembling that of the Google Chrome web browser. Since Google Chrome OS is aimed at users who spend most of their computer time on the Web, the only application on the device is a browser incorporating a media player and a file manager.[4][6][7][8][9]

The launch date for retail hardware featuring Chrome OS slipped after Google first announced the operating system: from an initial forecast date in late 2010 to June 15, 2011, when "Chromebooks" from Samsung (and then Acer in July) actually shipped.[10][11][12][13][14]

Contents

[edit] History

Former Google engineer Jeff Nelson wrote the first version of the operating system, code named "Google OS", in 2006. He based it on a Linux distribution and the Firefox browser, as Google's own Chrome browser was not yet available. The impetus was speed. Nelson thought that both Windows and Linux were needlessly slow. His solution was to move the operating system off the hard disk and into RAM. Restarting Firefox, he recalls, "went from ~45 seconds to ~1 second. Browsing a directory in the file explorer went from ~8 seconds to ~0.01 seconds. Even compiling code became 60% faster, and I could run non-indexed, recursive greps of the entire RAM resident file system in under 15 seconds. Try doing that with a hard disk." Because of the size constraints of RAM, the operating system relied on applications that resided on the Internet and stored user data online. Nelson filed a patent for his invention, titled "Network-based Operating System Across Devices," on March 20, 2009. It was granted in August 7, 2012 and assigned to Google long after he departed the company.[15][16]

To ascertain marketing requirements for an operating system focused on netbook Web transactions, Google did not do the usual demographic research generally associated with a large software development project. Instead, engineers relied on more informal metrics, including monitoring the usage patterns of some 200 Chrome OS machines used by Google employees. Developers also noted their own usage patterns. Matthew Papakipos, former[17] engineering director for the Chrome OS project, put three machines in his house and found himself logging in for brief sessions: to make a single search query or send a short email.[6]

On November 19, 2009, Google released Chrome OS's source code as the Chromium OS project.[4] As with other open source projects, developers are modifying code from Chromium OS and building their own versions, whereas Google Chrome OS code will only be supported by Google and its partners, and will only run on hardware designed for the purpose. Unlike Chromium OS, Chrome OS will be automatically updated to the latest version.[18] InformationWeek reviewer Serdar Yegulalp wrote that Chrome OS will be a product, developed to "a level of polish and a degree of integration with its host hardware that Chromium OS does not have by default," whereas Chromium OS is a project, "a common baseline from which the finished work is derived" as well as a pool for derivative works. The product and project will be developed in parallel and borrow from each other.[19]

At a November 19, 2009 news conference, Sundar Pichai, the Google vice president overseeing Chrome, demonstrated an early version of the operating system. He previewed a desktop which looked very similar to the Chrome browser, and in addition to the regular browser tabs also had application tabs, which take less space and can be pinned for easier access. At the conference, the operating system booted up in seven seconds, a time Google said it would work to reduce.[18][20][19][21]

Also on November 19, 2009, Chris Kenyon, vice president of OEM services at Canonical Ltd announced that Canonical "is contributing engineering to Google [Chrome OS] under contract. In our discussions, Sundar Pichai and Linus Upson made it clear that they want, wherever feasible, to build on existing components and tools from the open source community without unnecessary re-invention. This clear focus should benefit a wide variety of existing projects and we welcome it."[22]

On January 25, 2010, Google posted notes, images and a video of a conceptual design showing how a Chrome OS user interface might look on a tablet computer with a 5–10 inch screen. The design would include the same basic layout as on netbooks, but with a touch interface; an onscreen qwerty keyboard in different layouts; large, square icons placed above the tabs; and panels placed along the bottom edge that could be opened with an upward dragging motion.[23][24] The posting was made two days before Apple announced the iPad tablet.[25] On March 16, 2011, several changes to Chromium OS were made which indicate the development of a tablet version of Google Chrome OS.[26]

In March 2010, Google indicated that consideration is being given to developing two versions of the operating system, a consumer version and an enterprise version.[27]

Google was granted a patent for "Network Based Operating System Across Devices" on August 7, 2012 with inventor Jeffrey Nelson.[16] Wolfgang Gruener of Tom's Hardware criticized the patent as too broad, covering all cloud operating systems.[28]NDICIO Research wrote that the patent, which followed Google's acquisition of Motorola Mobility, "is the best sign yet that Google is working toward seamless hardware and software experiences."[29]

[edit] Cr-48 prototype hardware

The Cr-48 showing the setup screen seen when first booting up a Chromebook

At a December 7, 2010 press briefing, Google announced the Cr-48 laptop, a reference hardware design to test the Chrome OS operating system. It was named after Chromium-48, an unstable isotope of the metallic element known as Chromium.[30] The laptop's design broke convention by replacing the caps lock key with a dedicated search key.[31]

The Cr-48 was intended for testing only, not retail sales.[32][33][34] Google addressed complaints that the operating system offers little functionality when the host device is not connected to the Internet. The company demonstrated an offline version of Google Docs running on Chrome OS and announced a 3G plan that would give Chrome OS users 100 MB of free data each month, with additional paid plans available from Verizon.[13]

About 60,000 Cr-48s were distributed to testers and reviewers in early December 2010. Reviews of Chrome OS running on the Cr-48 in mid-December 2010 indicated that while the project held promise, it still had some distance to go before being ready for market.[35][36]

On March 8, 2011, Google Product Management vice president Sundar Pichai stated that the last of the 60,000 Cr-48s had been shipped.[37]

The Cr-48 notebooks have additional unused hardware components for implementation at a future date, including a Bluetooth 2.1 controller.[38] The USB port only acts as a keyboard, mouse, Ethernet adapter, or USB storage port and will not work as a printer port as there is no print stack on the operating system.[39] Adding further hardware outside of the previously mentioned items will likely cause problems with the operating system's "self knowing" security model.[40] Users are encouraged to use a secure service called Google Cloud Print to print to legacy printers connected to their desktop computers, or connect an HP ePrint, Kodak Hero, Kodak ESP, or Epson Connect printer to the Google Cloud Print service for a "cloud aware" printer connection.[41]

[edit] Commercial hardware: Chromebooks

Google initially named several development partners working on hardware for the operating system, with others named in the press, including Acer, Adobe, Asus, Freescale, Hewlett-Packard, Lenovo, Qualcomm, Texas Instruments, Toshiba,[42] Intel,[43] Samsung,[44][45] and Dell.[46]

On May 11, 2011 at its Google I/O developer conference, Google announced that the first two commercially available laptops incorporating Chrome OS would be manufactured by Acer Inc. and Samsung Electronics Co., with a retail price beginning at $349. The ship date was June 15 for the United States, the United Kingdom, France, Germany, Netherlands, Italy and Spain. The Chromebooks are sold in the United States through Amazon and Best Buy; internationally through "leading retailers". Google claimed an eight-second bootup time and eight-hour operation on one battery charge, and said that the chromebooks would require no virus protection. Models equipped with 3G connectivity receive 100 megabytes of wireless data per month, free for two years, with an additional gigabyte at $20 per month. Samsung created a Chrome OS desktop machine called a Chromebox.[14][47][48]

Google also announced a monthly payment scheme for business and education customers at $28 and $20 per user per month, respectively, for a three-year contract, including replacements and upgrades.[14]

On May 29, 2012, Google and Samsung introduced the Second-Generation Chromebook and a new compact desktop Chromebox, which was said to be a clone of the Apple Mac Mini.[49][50]

[edit] Relationship to Android

Google's successive introduction of the popular Android[51] and Google Chrome OS has put the company behind two open source, client-based operating systems. Microsoft CEO Steve Ballmer accused Google of not being able to make up its mind.[52] Google has suggested that the two operating systems address different markets, mobile and personal computing, which remain distinct despite the growing convergence of the devices. Google co-founder Sergey Brin suggested that the two systems "will likely converge over time."[53]

Steven Levy wrote that "the dissonance between the two systems was apparent" at the 2011 Google I/O developer conference. "Each day of the event featured a keynote devoted to one system followed by a press briefing where each team leader (Android's Andy Rubin and Chrome's Sundar Pichai) unconvincingly tried to explain why the systems weren't competitive. Co-founder Sergey Brin addressed the question by saying that owning two promising OS's was a problem that most companies would love to face".[54]

[edit] Design

Early in the project, Google put online many details of Chrome OS's design goals and direction.[55] But the company has not followed up with a technical description of the completed operating system.

[edit] User interface

Old Chrome-Chromium OS login screen

Design goals for Google Chrome OS's user interface included using minimal screen space by combining applications and standard Web pages into a single tab strip, rather than separating the two. Designers considered a reduced window management scheme that would operate only in full-screen mode. Secondary tasks would be handled with "panels": floating windows that dock to the bottom of the screen for tasks like chat and music players. Split screens were also under consideration for viewing two pieces of content side-by-side. Google Chrome OS would follow the Chrome browser's practice of leveraging HTML5's offline modes, background processing, and notifications. Designers proposed using search and pinned tabs as a way to quickly locate and access applications.[56]

[edit] New window manager and graphics engine

On April 10, 2012, a new build of Chrome OS offered a choice between the original full-screen window interface and overlapping, re-sizable windows, such as found on Microsoft Windows and Apple's Mac OS X. The feature was implemented through the Ash window manager, which runs atop the Aura hardware-accelerated graphics engine. The April 2012 upgrade also included the ability to display smaller, overlapping browser windows, each with its own translucent tabs, browser tabs that can be "torn" and dragged to new positions or merged with another tab strip, and a mouse-enabled shortcut list across the bottom of the screen. One icon on the task bar shows a list of installed apps and bookmarks. Writing in CNET, Stephen Shankland argued that with overlapping windows, "Google is anchoring itself into the past" as both iOS and Microsoft's Metro interface are largely or entirely full-screen. Even so, "Chrome OS already is different enough that it's best to preserve any familiarity that can be preserved".[57][58][59]

[edit] Architecture

In preliminary design documents for the Chromium OS open source project, Google described a three-tier architecture: firmware, browser and window manager, and system-level software and userland services.[60]

  • The firmware contributes to fast boot time by not probing for hardware, such as floppy disk drives, that are no longer common on computers, especially netbooks. The firmware also contributes to security by verifying each step in the boot process and incorporating system recovery.[60]
  • System-level software includes the Linux kernel that has been patched to improve boot performance. Userland software has been trimmed to essentials, with management by Upstart, which can launch services in parallel, re-spawn crashed jobs, and defer services in the interest of faster booting.[60]
  • The window manager handles user interaction with multiple client windows much like other X window managers.[60]

[edit] Remote application access and virtual desktop access

In June 2010, Google software engineer Gary Kačmarčík wrote that Chrome OS will access remote applications through a technology unofficially called "Chromoting", which would resemble Microsoft's Remote Desktop Connection.[61] The name has since been changed to "Chrome Remote Desktop", and is "probably closer to running an application via Remote Desktop Services or by first connecting to a host machine by using RDP or VNC".[62] Initial roll-outs of Chrome-OS laptops (Chromebooks) indicate an interest in enabling users to access virtual desktops.[63][64]

[edit] Hardware support

Google Chrome OS is initially intended for secondary devices like netbooks, not as a user's primary PC,[20] and will run on hardware incorporating an x86 or ARM-based processor.[7] While Chrome OS will support hard disk drives, Google has requested that its hardware partners use solid-state drives "for performance and reliability reasons"[18] as well as the lower capacity requirements inherent in an operating system that accesses applications and most user data on remote servers. In November 2009 Matthew Papakipos, engineering director for the Google Chrome OS claimed that the Chrome OS consumes one-sixtieth as much drive space as Windows 7.[65]

[edit] Integrated media player, file manager

Google integrates a media player into both Chrome OS and the Chrome browser, enabling users to play back MP3s, view JPEGs, and handle other multimedia files while offline.[61]

Chrome OS also includes an integrated file manager resembling those found on other operating systems, with the ability to display folders and their associated files, as well as preview and manage file contents using a variety of Web applications, including Google Docs and Box.net.[66]

The file manager in Chrome OS showing a mounted Google Drive. Google Drive integration in the file manager was introduced with Aura and Ash, in the spring of 2012.

[edit] Printing

Google Cloud Print is Google's proposed solution to help any application on any device to print on any printer. While the cloud provides virtually any connected device with information access, the task of "developing and maintaining print subsystems for every combination of hardware and operating system – from desktops to netbooks to mobile devices – simply isn't feasible."[67][68] However, the cloud service would entail installing a piece of software, called a proxy, as part of Chrome OS. The proxy would register the printer with the service, manage the print jobs, provide the printer driver functionality, and give status alerts for each job.[69]

[edit] Link handling

Chrome OS was designed with the intention of having user documents and files stored on online servers. However, both Chrome OS and the Chrome browser have unresolved decisions regarding handling specific file types offline. For example, if a JPEG is opened from a local storage device, should a specific Web application be automatically opened to view it, and if so, which one? Similarly, if a user clicks on a .doc file, which website should open: Microsoft Office Live, Gview, or a previewing utility? The project director at that time, Matthew Papakipos, noted that Windows developers have faced the same fundamental problem: "Quicktime is fighting with Windows Media Player, which is fighting with Chrome." As the number of Web applications increases, the same problem arises.[6]

[edit] Security

In March 2010, Google software security engineer Will Drewry discussed Chrome OS security. Drewry described Chrome OS as a "hardened" operating system featuring auto-updating and sandbox features that will reduce malware exposure. He said that Chrome OS netbooks will be shipped with Trusted Platform Module (TPM), and include both a "trusted bootpath" and a physical switch under the battery compartment that actuates a developer mode. That mode drops some specialized security functions but increases developer flexibility. Drewry also emphasized that the open source nature of the operating system will contribute greatly to its security by allowing constant developer feedback.[27]

At a December 2010 press conference, Google claimed that Chrome OS would be the most secure consumer operating system due in part to a verified boot ability, in which the initial boot code, stored in read-only memory, checks for system compromises.[13]

[edit] Shell access

Chrome OS includes the Chrome Shell, or "crosh", which offers minimal functionality such as ping and SSH, but no Bash-like shell abilities. In developer mode, a full-featured Bash shell can be opened via VT-2, and is also accessible via the crosh command "shell".[70]

[edit] Reception

Early on, Chrome OS was viewed as a competitor to Microsoft, both directly to Microsoft Windows and indirectly the company's word processing and spreadsheet applications—the latter through Chrome OS's reliance on cloud computing.[71][72] But Chrome OS engineering director Matthew Papakipos argued that the two operating systems would not fully overlap in functionality because Chrome OS hosted is intended for netbooks, which lack the computational power to run a resource-intensive program like Adobe Photoshop.[6]

Some observers claimed that other operating systems already fill the niche that Chrome OS is aiming for, with the added advantage of supporting native applications in addition to a browser. Tony Bradley of PC World wrote in November 2009: "We can already do most, if not all, of what Chrome OS promises to deliver. Using a Windows 7 or Linux-based netbook, users can simply not install anything but a web browser and connect to the vast array of Google products and other web-based services and applications. Netbooks have been successful at capturing the low-end PC market, and they provide a web-centric computing experience today. I am not sure why we should get excited that a year from now we'll be able to do the same thing, but locked into doing it from the fourth-place web browser."[73]

A year later, Ryan Paul of Ars Technica came to similar conclusions. He wrote that Google's Cr-48 prototype "met the basic requirements for Web surfing, gaming, and personal productivity, but falls short for more intensive tasks." He praised Google's approach to security, but wondered whether mainstream computer users would accept an operating system whose only application is a browser. "In its current form, I think that the operating system could appeal to some niche audiences, like regular consumers users who really just need browsing or office productivity workers at companies that have gone Google or only use intranet apps. It's decidedly not a full-fledged alternative to the general purpose computing environments that currently ship on netbooks." Paul wrote that most of Chrome OS's advantages "can be found in other software environments without having to sacrifice native applications."[35]

In reviewing the Cr-48 on December 29, 2010, Kurt Bakke of Conceivably Tech said: "in my household the Chromebook has turned into a family appliance and the most frequented computer in our household. Its 15 second startup time and dedicated Google user accounts made it the go-to device for quick searches, email as well as YouTube and Facebook activities. It has not turned into a device that can rival the appeal of any of our other notebooks – we have one gaming laptop, two mainstream notebooks and two netbooks in our household with five kids. The biggest complaint I heard was its lack of performance in Flash applications."[74]

In ongoing testing, Wolfgang Gruener, also writing in Conceivably Tech, said that cloud computing at cellular data speeds is unacceptable and that the lack of offline ability turns the Cr-48 "into a useless brick" when not connected.[75] "It's difficult to use the Chromebook as an everyday device and give up what you are used to on a Mac/Windows PC, while you surely enjoy the dedicated cloud computing capabilities occasionally."[76] He praised a March 2011 update that included new trackpad control features, scrolling support, power improvements and a large number of bug fixes.[77]

[edit] See also

[edit] References

  1. ^ "Kernel Design: Background, Upgrades". Google. http://www.chromium.org/chromium-os/chromiumos-design-docs/chromium-os-kernel. Retrieved September 7, 2011.
  2. ^ Google. "Google Chrome OS Terms of Service". http://www.google.com/intl/en/chromebook/termsofservice.html. Retrieved September 5, 2012.
  3. ^ Mediati, Nick (July 7, 2009). "Google Announces Chrome OS". PC World. http://www.pcworld.com/article/168028/google_announces_chrome_os.html. Retrieved July 8, 2009.
  4. ^ a b c Sengupta, Caesar (November 19, 2009). "Releasing the Chromium OS open source project". Official Google Blog. Google, Inc.. http://googleblog.blogspot.com/2009/11/releasing-chromium-os-open-source.html. Retrieved November 19, 2009.
  5. ^ Dylan F. Tweney (November 19, 2009). "Gadget Lab Hardware News and Reviews Google Chrome OS: Ditch Your Hard Drives, the Future Is the Web". Wired. http://www.wired.com/gadgetlab/2009/11/google-chrome-os-ditch-your-hard-drives-the-future-is-the-web/. Retrieved November 22, 2009.
  6. ^ a b c d Stokes, Jon (January 19, 2010). "Google talks Chrome OS, HTML5, and the future of software". Ars Technica. http://arstechnica.com/business/news/2010/01/chrome-os-interview-1.ars. Retrieved January 23, 2010.
  7. ^ a b Womack, Brian (July 8, 2009). "Google to Challenge Microsoft With Operating System". Bloomberg. http://www.bloomberg.com/apps/news?pid=20601087&sid=aTd2k.YdQZ.Y. Retrieved July 8, 2009.
  8. ^ Hansell, Saul (July 8, 2009). "Would you miss Windows with a Google operating system?". New York Times. http://bits.blogs.nytimes.com/2009/07/08/would-you-miss-windows-with-a-google-operating-system/. Retrieved July 8, 2009.
  9. ^ Pichai, Sundar (July 7, 2009). "Introducing the Google Chrome OS". Official Google Blog. Google, Inc.. http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html. Retrieved July 11, 2012.
  10. ^ "Google sets "late fall" release for Chrome". Reuters. June 2, 2010. http://www.reuters.com/article/idUSTRE65112220100602.
  11. ^ Ahmed, Murad (July 8, 2009). "Google takes on Microsoft with Chrome operating system". The Times (UK). http://technology.timesonline.co.uk/tol/news/tech_and_web/article6665703.ece. Retrieved July 8, 2009.
  12. ^ Boulton, Clint (November 2010). "Google CEO Schmidt on Google TV, Chrome OS, NFC Chip". Google Watch. http://googlewatch.eweek.com/content/google_strategy/googles_schmidt_on_google_tv_chrome_os_nfc_chip_concept.html. Retrieved November 19, 2010.
  13. ^ a b c Paul, Ryan (December 2010). "Google demos Chrome OS, launches pilot program". Ars Technica. http://arstechnica.com/gadgets/guides/2010/12/google-demos-chrome-os-launches-pilot-program.ars. Retrieved December 8, 2010.
  14. ^ a b c Sherr, Ian (May 11, 2011). "Google to launch Chrome Laptops in June". Wall Street Journal. http://online.wsj.com/article/SB10001424052748703730804576317361801753874.html. Retrieved May 11, 2011.
  15. ^ Nelson, Jeff (November 13, 2012). "Inventing Chromebook". In the Clouds (Jeff Nelson blog). http://blog.jeff-nelson.com/2012/11/on-inventing-chromebook.html. Retrieved 26 November 2012.
  16. ^ a b "Network based operating system across devices". United States Patent: Nelson. United States Patent and Trademark Office. http://patft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=8,239,662.PN.&OS=PN/8,239,662&RS=PN/8,239,662. Retrieved 26 November 2012.
  17. ^ Brodkin, Jon (June 28, 2010). "Google Chrome OS creator takes job at Facebook, announces switch on Twitter". Business Week. http://www.networkworld.com/news/2010/062810-google-chrome-creator-facebook.html. Retrieved June 29, 2010.
  18. ^ a b c "Developer FAQ". Google. http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/developer-faq. Retrieved December 12, 2009.
  19. ^ a b Yegulalp, Serdar (December 5, 2009). "Google Chrome OS Previewed". InformationWeek. http://www.informationweek.com/news/software/operatingsystems/showArticle.jhtml?articleID=222000239. Retrieved December 6, 2009.
  20. ^ a b "Linux commands". The New York Times. http://www.nytimes.com/2009/11/20/technology/n.
  21. ^ Rapoza, Jim (December 3, 2009). "REVIEW: Google Chrome OS Developer Edition Provides Intriguing Look at Web-Only Computing". eWeek.com. http://www.eweek.com/c/a/Application-Development/REVIEW-Google-Chrome-OS-Developer-Edition-Provides-Intriguing-Look-at-WebOnly-Computing-446612/. Retrieved December 4, 2009.
  22. ^ Kenyon, Chris (November 2009). "Google Chrome OS and Canonical". Canonical Blog. http://blog.canonical.com/?p=294. Retrieved December 14, 2010.
  23. ^ "Form Factors Exploration". The Chromium Projects. Google. http://dev.chromium.org/chromium-os/user-experience/form-factors. Retrieved February 10, 2010.
  24. ^ "Form Factor Exploration: Tablet". The Chromium Projects. Google. January 25, 2010. http://dev.chromium.org/chromium-os/user-experience/form-factors/tablet. Retrieved February 10, 2010.
  25. ^ Goldman, David (February 4, 2010). "Tablet wars: Google looks to take on Apple iPad". CNNMoney.com. http://money.cnn.com/2010/02/04/technology/apple_ipad_google_chrome/. Retrieved February 10, 2010.
  26. ^ "Google begins tablet version of Chrome OS". CNET News. April 4, 2011. http://news.cnet.com/8301-30685_3-20051228-264.html. Retrieved April 8, 2011.
  27. ^ a b Messmer, Ellen (March 2010). "Google sheds light on Chrome OS Netbook security". http://www.itworld.com/security/99227/google-sheds-light-chrome-os-netbook-security?source=smlynch. Retrieved March 8, 2010.
  28. ^ "Google Gets Umbrella Patent For Cloud Operating Systems". http://www.tomshardware.com/news/google-cloud-chrome-os-patent,16808.html.
  29. ^ "Google Patents the Cloud OS". NDICIO Research. August 10, 2012. http://www.ndicio.com/google-was-just-granted-the-cloud-os-patent/. Retrieved 26 November 2012.
  30. ^ Metz, Cade (December 10, 2010). "Google Cr-48: Inside the Chrome OS 'unstable isotope'". http://www.theregister.co.uk/2010/12/14/google_chrome_os_cr_48/. Retrieved January 4, 2012.
  31. ^ Diaz, Jesus (December 7, 2010). "Google wants to take your Caps Lock key away". Gizmodo. http://gizmodo.com/5708638/. Retrieved December 7, 2010.
  32. ^ Ackerman, Dan (December 7, 2010). "Google Cr-48 Chrome hardware pilot program: "Not for the faint of heart"". CNET News. http://news.cnet.com/8301-17938_105-20024897-1.html. Retrieved December 8, 2010.
  33. ^ Calore, Michael (December 2010). "First Look: Google's Netbook Has Its Head in the Cloud". Wired. http://www.wired.com/gadgetlab/2010/12/cr-48-chrome-os-first-look/?pid=888&viewall=true. Retrieved December 10, 2010.
  34. ^ Google (December 2010). "Cr-48 Chrome Notebook". http://www.google.com/chromeos/pilot-program-cr48.html. Retrieved December 13, 2010.
  35. ^ a b Paul, Ryan (December 2010). "Nothing but 'Net: hands-on with the Cr-48 Chrome OS laptop". Ars Technica. http://arstechnica.com/open-source/reviews/2010/12/nothing-but-net-hands-on-test-of-the-cr-48-chrome-os-laptop.ars. Retrieved December 16, 2010.
  36. ^ Gruener, Wolfgang (December 2010). "Chrome OS Is Ahead Of Its Time". Conceivably Tech. http://www.conceivablytech.com/4624/products/chrome-os-is-ahead-of-its-time/. Retrieved December 14, 2010.
  37. ^ Pichai, Sundar (March 2011). "sundarpichai". Twitter. http://www.twitter.com/sundarpichai#. Retrieved March 20, 2011.
  38. ^ "CR48 Prototype Hardware Specs – Chrome OS Lounge". http://www.chromeoslounge.com/cr-48-chrome-notebook/207-google-cr-48-notebook-*full*-hardware-specs.html. Retrieved April 18, 2011.
  39. ^ "Google Cloud Print Help". http://www.google.com/support/chromeos/bin/answer.py?answer=1069693. Retrieved April 18, 2011.
  40. ^ "YouTube – Chrome OS Security". http://www.youtube.com/watch?v=A9WVmNfgjtQ. Retrieved April 18, 2011.
  41. ^ "Google Cloud Print". http://www.google.com/cloudprint/learn/printers.html#setup-hp#setup-kodak#setup-epson. Retrieved April 19, 2011.
  42. ^ Pichai, Sundar (July 8, 2009). "Google Chrome OS FAQ". Official Google Blog. Google, Inc.. http://chrome.blogspot.com/2009/07/google-chrome-os-faq.html. Retrieved July 21, 2009.
  43. ^ Myslewski, Rik (July 10, 2009). "Intel Cozying up to Google Chrome OS". The RegisterOSnews. http://www.osnews.com/story/21812. Retrieved July 11, 2012.
  44. ^ Richards, David (February 11, 2010). "Samsung Confirms Chrome Based Netbook". Channel News Australia. http://www.channelnews.com.au/Hardware/Mobility/T3H4L5C6. Retrieved February 13, 2010.
  45. ^ "Google Chrome OS gets detailed, first laptops from Acer and Samsung coming mid-2011". engadget. December 7, 2010. http://www.engadget.com/2010/12/07/google-chrome-os-gets-detailed/. Retrieved December 11, 2010.
  46. ^ Ricadela, Aaron (June 25, 2010). "Dell Tests Google's Chrome Operating System on Some Computers". Bloomberg News. http://www.bloomberg.com/news/2010-06-25/dell-tests-google-s-chrome-operating-system-on-netbook-tablet-computers.html. Retrieved September 5, 2010.
  47. ^ "A new kind of computer: Chromebook". The Official Google Blog. Google. http://googleblog.blogspot.com/2011/05/new-kind-of-computer-chromebook.html. Retrieved May 14, 2011.
  48. ^ Stein, Scott (May 11, 2011). "First Take: Samsung Series 5 Chromebook, the future of Netbooks?". CNET News. http://news.cnet.com/first-take-samsung-series-5-chromebook-the-future-of-netbooks-hands-on-video/8301-17938_105-20061890-1.html. Retrieved May 14, 2011.
  49. ^ "SAMSUNG And Google Introduce The Second-Generation Chromebook and The World's First Chromebox". Samsung. May 29, 2012. http://www.samsung.com/us/news/20179. Retrieved September 5, 2012.
  50. ^ Hecei, Dave (July 2, 2012). "Google Chromebox Mac Mini Clone". The Post-Journal. http://www.post-journal.com/page/blogs.detail/display/1081/Google-Chromebox-Mac-Mini-Clone.html. Retrieved September 5, 2012.
  51. ^ Dignan, Larry (November 23, 2009). "Admob: Droid and Android army make big browsing splash". ZDNet. http://blogs.zdnet.com/BTL/?p=27711. Retrieved December 1, 2009.
  52. ^ Patel, Nilay (July 14, 2009). "Steve Ballmer calls Chrome OS "highly interesting," says Google "can't make up their mind"". AOL (Engadget). http://www.engadget.com/2009/07/14/steve-ballmer-calls-chrome-os-highly-interesting-says-google/. Retrieved November 28, 2009.
  53. ^ Krazit, Tom (November 20, 2009). "Brin: Google's OSes likely to converge". CNET News. http://news.cnet.com/8301-30684_3-10402653-265.html. Retrieved November 28, 2009.
  54. ^ Levy, Steven (June 7, 2011). "Jobs to PC: 'You're Busted!' And Other Notes From The OS Wars". Wired. http://www.wired.com/epicenter/2011/06/apple-jobs-os-wars/. Retrieved June 7, 2011.
  55. ^ "The Chromium Projects: Chrome OS". http://www.chromium.org/chromium-os. Retrieved July 2, 2011.
  56. ^ "The Chromium Projects: User Experience". Google. http://www.chromium.org/chromium-os/user-experience. Retrieved November 21, 2009.
  57. ^ Stephen Shankland (April 10, 2012). "Google gives Chrome OS a less alienating interface". CNET. http://news.cnet.com/8301-17939_109-57411748-2/google-gives-chrome-os-a-less-alienating-interface/.
  58. ^ Caleb Garling (April 10, 2012). "Google Chrome OS Busts Out Of Browser With New Interface". Wired. http://www.wired.com/wiredenterprise/2012/04/google-chrome-microsoft-apple/.
  59. ^ Paul, Ryan (April 16, 2012). "Hands-on: getting work done with Google's new Aura interface for Chrome OS". Ars Technica. http://arstechnica.com/gadgets/reviews/2012/04/hands-on-getting-work-done-with-googles-new-aura-interface-for-chrome-os.ars. Retrieved April 17, 2012.
  60. ^ a b c d "Security Overview: Chromium OS design documents". Google. http://sites.google.com/a/chromium.org/dev/chromium-os/chromiumos-design-docs/security-overview. Retrieved November 25, 2009.
  61. ^ a b Metz, Cade (June 9, 2010). "Google morphs Chrome OS into netbook thin client". The Register. http://www.theregister.co.uk/2010/06/09/google_to_include_remote_access_in_chrome_os/. Retrieved June 14, 2010.
  62. ^ Mathews, Lee (August 13, 2010). "Google Chrome's Remoting feature shows up in Chromium with enterprise implications". http://www.downloadsquad.com/2010/08/13/google-chrome-os-remoting/. Retrieved August 22, 2010.
  63. ^ Claburn, Thomas. "Google Pleased With Chromebook Sales". InformationWeek. http://www.informationweek.com/news/internet/google/230800190/.
  64. ^ Thibodeau, Patrick. "Orlando tries out 600 Chromebooks, The Chrome OS-based laptops may fit into city's cloud strategy". Computerworld. http://www.computerworld.com/s/article/9217920/Orlando_tries_out_600_Chromebooks?taxonomyId=77.
  65. ^ Mearian, Lucas (November 19, 2009). "Google Chrome OS will not support hard-disk drives". Computerworld. http://www.computerworld.com/s/article/9141191/Google_Chrome_OS_will_not_support_hard_disk_drives. Retrieved November 21, 2009.
  66. ^ Rosenblatt, Seth (August 10, 1011). "Chrome OS goes offline, gets file manager". CNET download.com. http://download.cnet.com/8301-2007_4-20062001-12.html. Retrieved August 11, 2011.
  67. ^ Jazayeri, Mike (April 15, 2010). "A New Approach to Printing". The Chromium Blog. Google Inc.. http://blog.chromium.org/2010/04/new-approach-to-printing.html. Retrieved April 16, 2010.
  68. ^ Heater, Brian (April 16, 2010). "Google Talks Cloud-Based Printing for Chrome OS". App Scout. http://www.appscout.com/2010/04/google_talks_up_cloud-based_pr.php. Retrieved April 16, 2010.
  69. ^ Whitney, Lance. "Google moving closer to Chrome OS printing". CNET News. http://news.cnet.com/8301-1023_3-20002680-93.html. Retrieved April 17, 2010.
  70. ^ "Poking around your Chrome OS Notebook". The Chromium Projects. http://www.chromium.org/chromium-os/poking-around-your-chrome-os-device. Retrieved February 6, 2011.
  71. ^ Keegan, Victor (July 10, 2009). "Can Chrome steal Microsoft's shine?". The Guardian (UK). http://www.guardian.co.uk/commentisfree/2009/jul/10/google-chrome-microsoft. Retrieved July 11, 2009.
  72. ^ Bertolucci, Jeff (July 10, 2009). "Google, Microsoft Invade Enemy Territory: Who Wins?". PC World. http://www.pcworld.com/article/168246/google_microsoft_invade_enemy_territory_who_wins.html. Retrieved July 11, 2009.
  73. ^ Bradley, Tony (April 2010). "Five Reasons the Google Chrome OS will Flop". http://www.pcworld.com/businesscenter/article/182739/Five_Reasons_the_Google_Chrome_OS_will_Flop.html. Retrieved April 21, 2010.
  74. ^ Bakke, Kurt (December 2010). "Where Did All Those Chromebooks Go To?". Conceivably Tech. http://www.conceivablytech.com/4803/products/where-did-all-those-chromebooks-go-to/. Retrieved December 30, 2010.
  75. ^ Gruener, Wolfgang (January 2011). "When Google's Cr-48 Truly Sucks". Conceivably Tech. http://www.conceivablytech.com/5243/products/when-google%E2%80%99s-cr-48-truly-sucks. Retrieved March 2, 2011.
  76. ^ Gruener, Wolfgang (February 2011). "Cr-48 and Chrome OS: When You Really Hate Netflix". Conceivably Tech. http://www.conceivablytech.com/5863/business/cr-48-and-chrome-os-when-you-really-hate-netflix. Retrieved March 2, 2011.
  77. ^ Gruener, Wolfgang (March 2011). "Google Releases First Big Chrome OS Update". Conceivably Tech. http://www.conceivablytech.com/5986/products/google-releases-first-big-chrome-os-update. Retrieved March 4, 2011.

[edit] External links