Language Selection

English French German Italian Portuguese Spanish

10 Mistakes Google Is Making with Chrome OS

Filed under
Google

As 2009 comes to an end and the technology industry looks ahead to 2010, it's Chrome OS that could arguably steal the show in the new year. It will be the first desktop operating system Google has ever released. It will also be released with one goal in mind: to beat Windows 7 wherever and whenever it can.

That's a tall order, for sure. Microsoft reigns supreme in the operating-system space. Windows 7, unlike its predecessor Windows Vista, has an opportunity to solidify Microsoft's position in the market with an experience that bests other operating systems on the market. So as Google prepares its Chrome OS for the market, it can't make any mistakes. The more mistakes the company makes, the more difficult it will be for Google to compete. Simply put, Microsoft has applied pressure that will dictate Google's moves going forward.

However, Google has already made mistakes. The search giant is focused on the wrong things. And it could come back to haunt it. Let's take a look at some of the mistakes Google has made.

1. No Chrome OS netbook




Top 10 Google Stories of 2009

eweek.com: It would be an understatement to opine that 2009 was a big year for Google. With many businesses still laying employees off and struggling to retrench from the tough recession, the search engine flourished. Google unveiled several new products, made acquisitions and eyed new markets, including a plan to offer Chrome Operating System on netbooks in 2010.

In this slideshow, eWEEK recaps Google's busy year.

5 Ways Google Could Drop the Open-Source Ball

maximumpc.com: What a year for Google! But instead of waxing nostalgic about all of "The Goog's" fancy Web-based services or search refinements or what-have-you, I think it's important to note just how dramatically Google has made its mark on the open-source world in 2009.

Yes, I'm talking about Chrome. Or Android. Or Chrome-Android. You know, those two independent-but-not-really operating systems that are different yet similar enough to warrant Google splitting them with a wink-and-a-nod that they'll likely be combined at some grand point in the future.

For all the intelligence packed into the dark recesses of Google's worldwide campuses, the company doesn't have a walk-in-the-park path to victory in the mobile, desktop, or laptop markets with its bevy of open-source operating systems.

Here's why:

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: OSS

  • Anonymous Open Source Projects
    He made it clear he is not advocating for this view, just a thought experiment. I had, well, a few thoughts on this. I tend to think of open source projects in three broad buckets. Firstly, we have the overall workflow in which the community works together to build things. This is your code review processes, issue management, translations workflow, event strategy, governance, and other pieces. Secondly, there are the individual contributions. This is how we assess what we want to build, what quality looks like, how we build modularity, and other elements. Thirdly, there is identity which covers the identity of the project and the individuals who contribute to it. Solomon taps into this third component.
  • Ostatic and Archphile Are Dead
    I’ve been meaning to write about the demise of Ostatic for a month or so now, but it’s not easy to put together an article when you have absolutely no facts. I first noticed the site was gone a month or so back, when an attempt to reach it turned up one of those “this site can’t be reached” error messages. With a little checking, I was able to verify that the site has indeed gone dark, with writers for the site evidently losing access to their content without notice. Other than that, I’ve been able to find out nothing. Even the site’s ownership is shrouded in mystery. The domain name is registered to OStatic Inc, but with absolutely no information about who’s behind the corporation, which has a listed address of 500 Beale Street in San Francisco. I made an attempt to reach someone using the telephone number included in the results of a “whois” search, but have never received a reply from the voicemail message I left. Back in the days when FOSS Force was first getting cranked up, Ostatic was something of a goto site for news and commentary on Linux and open source. This hasn’t been so true lately, although Susan Linton — the original publisher of Tux Machines — continued to post her informative and entertaining news roundup column on the site until early February — presumably until the end. I’ve reached out to Ms. Linton, hoping to find out more about the demise of Ostatic, but haven’t received a reply. Her column will certainly be missed.
  • This Week In Creative Commons History
    Since I'm here at the Creative Commons 2017 Global Summit this weekend, I want to take a break from our usual Techdirt history posts and highlight the new State Of The Commons report that has been released. These annual reports are a key part of the CC community — here at Techdirt, most of our readers already understand the importance of the free culture licensing options that CC provides to creators, but it's important to step back and look at just how much content is being created and shared thanks to this system. It also provides some good insight into exactly how people are using CC licenses, through both data and (moreso than in previous years) close-up case studies. In the coming week we'll be taking a deeper dive into some of the specifics of the report and this year's summit, but for now I want to highlight a few key points — and encourage you to check out the full report for yourself.
  • ASU’s open-source 'library of the stars' to be enhanced by NSF grant
  • ASU wins record 14 NSF career awards
    Arizona State University has earned 14 National Science Foundation early career faculty awards, ranking second among all university recipients for 2017 and setting an ASU record. The awards total $7 million in funding for the ASU researchers over five years.

R1Soft's Backup Backport, TrustZone CryptoCell in Linux

  • CloudLinux 6 Gets New Beta Kernel to Backport a Fix for R1Soft's Backup Solution
    After announcing earlier this week the availability of a new Beta kernel for CloudLinux 7 and CloudLinux 6 Hybrid users, CloudLinux's Mykola Naugolnyi is now informing us about the release of a Beta kernel for CloudLinux 6 users. The updated CloudLinux 6 Beta kernel is tagged as build 2.6.32-673.26.1.lve1.4.26 and it's here to replace kernel 2.6.32-673.26.1.lve1.4.25. It is available right now for download from CloudLinux's updates-testing repository and backports a fix (CKSIX-109) for R1Soft's backup solution from CloudLinux 7's kernel.
  • Linux 4.12 To Begin Supporting TrustZone CryptoCell
    The upcoming Linux 4.12 kernel cycle plans to introduce support for CryptoCell hardware within ARM's TrustZone.

Lakka 2.0 stable release!

After 6 months of community testing, we are proud to announce Lakka 2.0! This new version of Lakka is based on LibreELEC instead of OpenELEC. Almost every package has been updated! We are now using RetroArch 1.5.0, which includes so many changes that listing everything in a single blogpost is rather difficult. Read more Also: LibreELEC-Based Lakka 2.0 Officially Released with Raspberry Pi Zero W Support

Leftovers: Gaming