But now that the news is out, has Chrome OS lost its shine? People had high expectations for Google's new operating system but the end result doesn't look like the revolutionary, "change the world" product many had hoped for.

Don't get us wrong - Google's OS is different than whatever Windows, Mac, or Linux build you have running on your computer today. The new OS does away with desktop applications entirely - everything you use on Google Chrome OS runs on the web. Of course, the company hopes you'll use a lot of Google products like Gmail and YouTube, but it doesn't limit you to just Google-branded services. In the built-in applications area, there are also links to other web apps like the online TV streaming service Hulu.com and music sites Lala and Pandora. To be fair, Chrome OS even links to Yahoo and Microsoft's webmail offerings right out of the box.

Google's major goal with Chrome OS is to moving computing off our personal hard drives and into the cloud...the Google cloud. To accomplish such a feat, they've made the web browser the OS. Everything you need (in theory) is accessible through the included Google Chrome browser, the same browser the company currently offers to Windows users with Mac and Linux versions expected by the end of this year.

As exciting as that vision is, we have to wonder if people - especially the mainstream netbook users the OS is aimed at - are ready for this big of a switch. And more importantly, is the technology itself ready to make the change a comfortable and seamless experience?

...but is it Better?

After digesting yesterday's news, some lingering questions remain. Was this the OS everyone was hoping for or has Google let us down?

You Can't Just Install Chrome OS - You Have to Buy a New Netbook

To begin with, one of the more surprising reveals that came out of yesterday's news is that the OS cannot be installed on your own computer. Oh sure, there are downloads available that use Google's open-sourced code to create bootable builds tech-savvy users and developers can play with, but the official word from the search giant is that anyone wanting to use the "real" Google Chrome OS will have to purchase a new netbook to do so. You cannot simply download it from the web and install it on any machine.

Part of the reason for this restriction is driver support. Google is working with carefully selected manufacturers to offer a handful of netbooks running the OS in the coming year. By going this route, they don't have to provide an entire ecosystem of drivers for every piece of hardware out there - they can pick and choose which ones to support. They'll likely limit the number of peripherals supported, too. According to what was said yesterday, the company will support "mass storage devices" (think USB flash drives and digital cameras) but were cagey on how they plan on offering printing support. All they would say is that they're planning on an "innovative approach" when it comes to printing, whatever that means. Hopefully, they're planning to do something more than just integrating with Kinko's and FedEx's online document services, for example. Printing, (sorry Google) is not a web app just yet.

No Other Web Browsers Supported

Another big disappointment is the company's decision to limit all web surfing to the one included browser, Google Chrome. Firefox and Safari users are out of luck - no other browsers will be supported. But before you cry out "antitrust!," be warned - Google has this covered. The code base used to build the OS is open-source - that means anyone take the code and create their own version of Chrome OS. As was carefully - and haltingly - explained by Google's VP of Product Management, Sundar Pichai, other browser makers can take the code and build their own OS if they want to. But let's get real - Firefox Chrome OS? We don't think so. The reality is that fans of other browsers are simply out of luck if they want to use this operating system.

Offline Access is Limited. Your New Netbook is Now a Brick.

One of the questions that got glossed over during the Q&A session at the end of the event is how Google's OS plans to deal with offline access. The world is not blanketed in Wi-Fi yet, so what can this web-based OS do without the web? Surprisingly, the answer given didn't refer to any subsidized deals with cellular providers regarding deals to offer built-in 3G connectivity for the new netbooks. Instead, Pichai explained that the OS was built for use with Wi-Fi.

Of course, a handful of Google products use Google Gears, a technology that makes websites available offline. For example, Gmail uses Gears to create an offline version of your webmail inbox which you can use to read and respond to email until internet connectivity becomes available again. At that point, all the changes are synced back to Google's servers. Although Google didn't specifically refer to Gears when answering the question, there's no reason to doubt that it will work in Chrome OS's web browser the same as it does now in the standard Chrome browser.

However, Pichai did make note of Chrome OS's support for HTML5, an upcoming revision to the core markup language used to build the web. In the new specification, a key feature is offline support for web apps. However, web application developers will have to rebuild their apps in order to use HTML5, so users will be dependent on each individual company to make this change. While it's believed that one day this spec could make the whole web an offline app, the reality is that most developers have yet to implement this technology in their services yet. Even by Chrome OS's launch next year, there's no reason to believe the landscape will have changed significantly by then.

Do You Really Need an OS or Just the Chrome Web Browser?

Finally, the big question regarding Chrome OS is why? What can the OS do that any operating system running the Chrome browser cannot? Based on what was shown yesterday, the answer is very little. Chrome OS's brand-new features consist of two things: application tabs and panels. The panels are persistent windows that pop-up in front of your web browser's main window. For example, Google Chat, the company's IM service, can live in a panel that stays on top no matter what window you're viewing.

Application tabs, meanwhile, are special tabs that give you easy access to your most frequently used web apps from the browser. Any page tab can be made into an application tab with one click and the resulting "tab" is represented with the colorful icon for that site or service. While that's certainly a cool feature, it alone isn't a major selling point for the OS. That would be like saying you have to buy Mac OS X because of the dock or Windows because of the taskbar. You need a million of these little features combined to add up to a compelling reason to buy an OS.

That's not to say that Chrome OS itself doesn't have worthwhile features of its own - like its built-in security mechanisms or its auto-update system, it's just that these aren't the kinds of things that sell it to an end user. The questions consumers want answers to are what does it do that's special? What does it look like? And for now, the answer is "it's basically just a web browser."

Revolution? Maybe Not Just Yet.

At the end of the day, Chrome OS is an exciting, but not fully realized, vision. Although it has potential, the world may not be ready for a web-based netbook right now. Also, the technology needed to make the Wi-Fi only netbook useful without an internet connection isn't up to full speed either. At the end of the day, the netbook will be marginally more useful than an iPod Touch - when connected, it's amazing. Offline, not so much.

While you might not rush right out to buy a Chrome OS netbook when they first launch, there could come a time - sooner than you think - when it becomes a reasonable choice. When the majority of apps work offline and you've fully transitioned away from desktop apps, a web-connected netbook, especially one that's affordable, could easily become your everyday computer. That day hasn't arrived yet. For now, Chrome OS is an exciting glimpse at the future of computing, but not a practical device for the majority of users.

Disclosure: Sarah Perez freelances for Microsoft's Channel 10 blog, but is not a Microsoft employee. Her primary web browser is, in fact, Google Chrome which she uses exclusively.

Read on for our live updates from the event, which will start at 10:00 am PST.

9:55am: Ahead of the event, Google has already made the Chrome OS source code available.

10:00am: Still waiting for the event to begin. "Some of our attendees are unavoidably delayed in traffic."

10:05am: Event gets started. No beta, no devices today. But they will give a demo and focus on technical demo.

10:06am: Google Chrome has been open-sourced.

10:07am: Why did we do Chrome? We wanted to push the Web forward. It has over 40 million users.

Focus on speed. Mostly on the JavaScript engine, but also on other parts of the browser.

Updated Chrome over 20 times in the last year, but users didn't notice this because it happens in the background. User experience should be seamless.

Coming soon for Chrome: Chrome for Mac will be ready this year. Chrome for Linux is coming along "very well." Extensions are coming soon as well (with automatic updates).

10:10am: HTML5: we want Web application to get more access to the hardware. Example: graphics, multiple threads, real-time communication

10:12am: Three trends in the industry: netbooks, cloud (everything is a Web application today), phones getting computing capabilities

Phones are becoming more like laptops and laptops are becoming more like phones.

Chrome OS

10:15am: Chrome OS will be focused on speed, simplicity, security.

Every application on Chrome OS will be a Web application.

Simplicity: Chrome OS is just a browser - all your data is in the cloud. Users should be able to log into any Chrome OS machine and be up and running with their apps and data in seconds.

Security: users don't install binaries on the OS. Keeps the system safe. Everything runs in the browser.

10:18am: Demo time. Booting up on laptop takes seconds.

"Everybody knows how to use a browser, and we want Chrome OS to feel that way.

UI will continue to change until release.

Application tabs: just like tabs in Chrome, you will be able to set persistent tabs for apps (Gmail, etc.).

App menu in the top left to access apps as well (see first screenshot above). These apps will be little widgets that appear in a panel, just like Google Chat in Gmail.

10:23am: As netbooks get better, we expect them to become entertainment devices. Shows chess game.

Shows Google Books in full-screen mode.

Chrome OS will feature multiple windows. You can drag and drop tabs from one window to another.

Even the file browser is a Chrome tab. Shows what happens when you click on an Excel file. Actually launches Windows Live Office apps to show them.

"Every app you write for the Web is a Google Chrome OS app."

10:29am: Every file opens in the browser: PDF, Microsoft Office, etc.

Under the Hood

10:30am: Matthew Papakipos, Engineering Director for Google Chrome OS on stage now.

"We want Chrome OS to feel more like a television." Instant on - all flash memory.

How to make the boot-up faster?

Right now, operating systems still spend a lot of time on unnecessary boot steps (looking for floppy drives, etc.)

10:34am: Verified boot: makes sure all the components are working and haven't been modified by malware.

System automatically fixes itself and re-images the computer with the last working version; saves all system settings and cache data.

Security: all apps are Web apps. The OS does not trust any app.

Other security steps: files system is licked down; every tab runs in a secure sandbox. There is only a small list of known programs (verified and signed).

User data on a Chrome OS machine is always encrypted.

All the data is synced to the cloud (on the Google Drive?) - user partition on the machine is basically just a local cache.

10:41am: Back to Sundar Pichai, Vice President of Product Management.

Going to market: Chrome OS - but also working with hardware manufacturers.

Will only support flash drives - not traditional hard drives!

Google will specify reference hardware (specific Wi-Fi cards, etc.).

Google wants netbooks to have full-size keyboard, larger resolution, better trackpad.

Launch: Google wants devices to be out by next holiday season.

Chrome OS Open-Sourced

Google wants to work with open-source community. Will give all of its contributions back to the community.

10:45am: Shows marketing video.

Q&A

Question: What is the target group for a Chrome OS device? Will there be Chrome server solutions? Chrome as a server?

Answer: First we want to get netbooks out - no servers. But this is a paradigm shift in computer. Other questions: time will tell.

Question: Cost of Chrome OS netbooks?>

Answer: We will see larger netbooks - no price point - no price target. Demo ran on Asus EEE PC.

Question: How can manufacturers join the program?

Answer: Documentation is on website. Reaching out aggressively to hardware partners. For software developers, there will be a page that shows which devices are compatible already.

Question: Will there be an app store? Will Google certify drivers from OEMs? What about applications to edit photos?

Answer: App store: the Web is our app store, and we will work hard to make those discoverable. Drivers: working with hardware partners. Want devices to be built on reference devices and with open-source drivers. Editing: some apps are not available on the Web. Most people who will buy this machine will have another machine in their home. This is not meant to be a primary OS - just a "delightful experience to be on the Web." This is a companion device

Question: What about video codecs?

Answer: working on that. Trying to use hardware acceleration where possible. Everything that's available in Chrome will be available in Chrome OS - including the technology.

Sidenote: a lot of what you will see in Chrome OS will also flow back into the Chrome browser.

Question: Silverlight support?

Answer: No comment.

Question: Plugins? Other browsers?

Answer: code is available, but we won't support other browsers to run on Chrome OS.

Question: Do you expect to see this running only on netbooks or other devices as well?

Answer: more info about devices will come next year. Google is currently focused on delivering compelling devices: netbook-like form factors.

Question: How big is the OS?

Answer: nothing specific.

Question: Offline access? Google Gears support?

Answer: you can play media - but device is mainly meant to run online, though it will make use of HTML5 local storage.

Question: can you run it in a virtual machine?

Answer: yes.

Question: are you working with partners? Can Android apps run on Chrome OS?

Answer: we focus on making Web apps better. Mission of Chrome is to push Web apps forward. About Android apps: no.

Question: will there be third-party apps?

Answer: no. On phones you need native apps, but not on laptops.

Question: Native Client needs Intel - will you still support ARM?

Answer: we will support X86 and ARM - working on Native Client for ARM.

Question: What's the business model? Advertising in the browser?

Answer: Right now, we are focused on getting the OS and devices out. Chrome OS is free and open source. As people use the Web more, it benefits Google. No specific real estate in Chrome OS will be devoted to ads.

Question: What does Chrome do that I can't do in Firefox with plugins?

Answer: most of what we do is available in other browsers. But not the application tabs, etc. We are offering a fundamentally different model of computing (fast, simple, secure). In Chrome OS, Google can offer things others can't: fast boot, security.

Question: How do you get people to trust the cloud? How do you assure people that their data is secure?

Answer: most of what you are doing is already in the cloud - so problem is not specific to Chrome OS. Google thinks the cloud is just as secure as local storage. Users have a choice and are always in control.

Question: data syncing: will this be open or will data be controlled only by Google?

Answer: none

Sergey Brin drops in and joins the Q&A.

Question: Support for Java?

Answer: nothing to announce right now - hopefully we can do something interesting with this in the future.

Question: What about instant-on OS'es in Dell machines, etc.? Does Google want to do this?

Answer: No - we just want it to start up super-fast. A lean and mean netbook.

Question: Will a Chrome OS machine be able to run printers? Other devices?

Answer: we will support storage devices. Printers: we are taking an innovative approach and will share more about that next year.

Question: Open Source.

Answer: we want to upstream what we do and help the community.

Question: Real-time notifications.

Answer (Sergey Brin): We need better real-time notifications in the browser. Chrome will use the W3C Notifications API.

Question (for Sergey): How does Chrome OS fit into Google's strategy.

Answer: we want users to be able to use netbooks easily, and make it easy to manage software on these devices. The Web is the right platform for this. We're trying to fulfill this need.

For now, Image Swirl only works for about 200,000 queries, though Google plans to include more in the near future.

Better Photo Search Through Smarter Algorithms

This new feature takes image search to a new level, as it doesn't just display the most relevant images. Instead, Google notes, these "are the most relevant groups of images." To create these clusters of related images, Google analyzes the characteristics of the images themselves, but the algorithm also looks at meta tags and other clues in the description of these images. Google uses the same algorithms to find and organize images of landmarks in its index.

In an interview with eWeek, Google Image Swirl Product Manager Aparna Chennapragada said that this new service is part of Google's drive to "go beyond just relying on text." Bing introduced its visual search feature a few weeks ago and is still ahead of Google in bringing these features to its core search product.

Image Swirl makes looking for images on Google a far more interactive and fun experience. For now, Image Swirl is only a labs product - and some of the results can be a bit off at times - but chances are that this feature will find its way into the search options panel on Google Images in the future.

As Google points out in the announcement, finding these legal opinions has typically been difficult. Now, the company makes it very easy to find any legal opinion about Napster, for example. Google notes that it hopes that access to this information will allow regular citizens to "learn more about the laws that govern us all."

It's interesting to see that Google continues to add more and more public data to its repositories. Just last week, Google added data from the World Bank to its search results. Earlier this year, Google also started to include data from the U.S. Bureau of Labor Statistics and the U.S. Census Bureau's Population Division. Google didn't go as far as integrating these legal opinions on its search results page yet - though for searches for Roe v. Wade or Miranda v. Arizona, these results could really enhance the current search results.

But did the message get through to potential phone buyers? It appears that it did...at least according to mobile analytics firm Flurry. In their latest report, the company found that the Droid is now the fastest-selling Android phone to date, beating the sales of the myTouch 3G by more than four times.

Flurry's analytics service monitors over 10,000 mobile applications on both the iPhone and Android, or approximately two out of every three iPhone and Android handsets on the market. While obviously this isn't a look at the mobile ecosystem as a whole, it's a big enough slice to form some initial conclusions about the popularity of the latest mobile device to run Android, Google's mobile operating system.

By monitoring the new Android devices on Flurry's system, the company estimated the first-week sales for the Droid handsets as compared with both the myTouch 3G and Apple's iPhone 3GS. Although the iPhone still outsold the Droid within its first week, Flurry notes that the iPhone simultaneously launched in 8 countries worldwide while the Droid only launched in the U.S.

It's also important to note that the iPhone 3GS was just the latest model of the iPhone to arrive on the market, it is not the original device. Prior to the 3GS, the iPhone had two previous versions, the second which finally allowed for 3G cellular access and GPS capabilities. This update made the iPhone 3G a hugely popular upgrade and the company sold 1 million or so units on their opening weekend. Comparing the third generation iPhone to the first version of the Droid isn't a true "apples to apples" comparison, but on the other hand, the comparison of the T-Mobile myTouch 3G and the Droid is.

According to Flurry, Droid is dramatically outselling the myTouch 3G based on first week sales. That may say something about the quality of the Droid's hardware, the impact of a good marketing campaign or perhaps even people's frustrations with the iPhone's limitations. Or maybe a little of each. Then again, Verizon has nearly triple the number of subscribers as T-Mobile, so they already have a head start.

The Growing Power of Android

In the end, while we can't take any of these numbers to the bank, what we can learn is that the Android OS is making serious headway in the smartphone market. Although no one Android phone on its own may beat the iPhone, as more and more "worthy competitors" launch on numerous hardware platforms, the Android OS's install base may eventually catch up to that of the iPhone's. 

In any event, that's what Google believes. In a recent earnings call, Google CEO Eric Schmidt proclaimed that "Android adoption is about to explode," citing 12 Android phones on 32 carriers in 26 countries. Research firm Gartner predicts that the Android OS may end up ranking second worldwide by 2012. However, if more of the Android launches prove to be as successful as it appears the Droid's may be, Android may move up the charts even faster than predicted. Of course, who ends up on top all depends on Apple's next move. If the company decides to launch their phone on more carriers, all bets are off. If that's the case, Apple's market share could double, says Morgan Stanley's Kathryn Huberty. But that doesn't necessarily mean that Android would be left far behind. "Android is "backed by the power of Google's search engine," said Huberty. "Google's other up-and-coming consumer and enterprise products should make [Android] a dominant platform."

In today's announcement, Google stresses that SPDY is not a replacement for HTTP. It uses HTTP methods and headers, but it overrides the parts of the protocol that manage connections and data transfer formats.

Google will soon release its open-source SPDY-enabled Web server. The source code for the SPDY-enabled version of Chrome can be found here.

Creating a Faster and More Secure Web

According to the SPDY white paper, the project's goals are to reduce page load times by 50%, minimize deployment complexity and avoid the need for website owners to make any changes to their sites to implement SPDY. Instead, all the hard work will happen in the client and the Web server.

The team also wants SPDY to allow many concurrent HTTP requests to run across one TCP session and to make SSL the standard transport protocol.

Google clearly has an interest in making the Web experience as fast and secure as possible for its users. One of the reasons Google released its own browser was to get every other browser developer to focus on speed again. SPDY is even more ambitious. With SPDY, Google wants to change one of the most fundamental protocols on the Internet.

According to Google, these are the basic improvement of SPDY over HTTP:

• Multiplexed requests. There is no limit to the number of requests that can be issued concurrently over a single SPDY connection.  Because requests are interleaved on a single channel, the efficiency of TCP is much higher.
• Prioritized requests. Clients can request certain resources to be delivered first.  This avoids the problem of congesting the network channel with non-critical resources when a high-priority request is pending.
• Compressed headers.  Clients today send a significant amount of redundant data in the form of HTTP headers.  Because a single Web page may require 50 or 100 subrequests, this data is significant. Compressing the headers saves a significant amount of latency and bandwidth compared to HTTP.

Earlier this year, Google also added data from the U.S. Bureau of Labor Statistics and the U.S. Census Bureau's Population Division to its search results page. The queries that Google showcases in today's blog post (gdp of a country, internet users in the US or energy use in Iceland) are exactly the kind of queries where Wolfram Alpha excels. Currently, Bing doesn't display this kind of data from Wolfram Alpha and just focuses on math and nutrition, but a deeper integration between the two is just a matter of time.

Wolfram Alpha uses curated data sets - just like the World Bank or Census Bureau data - to compute its results. Google's current use of this data is less ambitious. Google wants to make public data more accessible - Wolfram Alpha wants to be a 'computational knowledge engine' that can manipulate these data sets.

Google Wants Your Public Data

One interesting aspect of today's blog post is that Google points out that there are "still many other data sets and sources out there, and we're excited about the possibilities for the future." Google also asks data publishers who are interested in making their data discoverable in Google to contact the company.

In the current implementation, Google can display results for the following types of questions:

CO2 emissions per capita, Electricity consumption per capita, Energy use per capita, Exports as percentage of GDP, Fertility rate, GDP deflator change, GDP growth rate, GNI per capita in PPP dollars, Gross Domestic Product, Gross National Income in PPP dollars, Imports as percentage of GDP, Internet users as percentage of population, Life expectancy, Military expenditure as percentage of GDP, Mortality rate, under 5, Population, and Population growth rate.

However, the system still only works with Gmail and the photo-sharing service Picasa. There's no mention of it expanding to encompass other Google services like Google Docs, for example. And there's definitely no mention of the seemingly mythical GDrive, the long-rumored online storage system supposedly under development which would allow for the upload of any file type for safe storage in the cloud. We're beginning to wonder: will Google ever offer us a real cloud storage solution?

Over on The Next Web, blogger Alex Wilhelm thinks the increased storage space hints at Google's future plans with their upcoming netbook operating system, Google Chrome OS. We have to admit, the same thought occurred to us as well. After all, netbooks don't typically have the same hard disk space as their larger, less totable counterparts. However, that's not always the case these days given the new middle-of-the-road offerings like the HP Mini 311, for example, which falls somewhere between an ultra-portable netbook and full-sized notebook with its 350 GB hard drive option.

But Alex has a point: by providing this type of cloud storage solution, netbooks can remain basic machines which are smaller and cost less. That would pave the way for the Google Chrome OS line of netbooks to be even more affordable devices than what's on the market today since they wouldn't need to come equipped with large hard drives.

Obviously, an OS-integrated cloud storage system of this nature would be a natural fit for Google's cloud operating system designed specifically for netbooks. And yet, it still seems to be an incomplete offering at this time.

But Still So Limited!

As much as we want to believe that the new changes are a sign of Google's plans for Chrome OS, it's just as possible that they're nothing more than the great discounts they appear to be. There's nothing all that new being introduced here - just better rates and more available space.

Sadly, the core storage offering itself is unchanged. It's still very limited, only encompassing Gmail and Picasa photos. What about the rest of our files - like the ones stored in Google Docs? What about our music and movie collections? What about the hundred or so of home videos we can't bear to delete from our hard drives? Google has no centralized solution for any of this yet. And many are beginning to wonder if they ever will.

In the tech community, there have been rumors about an all-encompassing online storage service called GDrive for years on end now, and yet, nothing has ever come of it. According to speculation (and wishful thinking), the supposed system would allow for the upload of all types of files and would tie together all of Google's services.

In our imaginations, we envision a dashboard that links us to our online Google Docs, our photos, our Gmail, our Google Sites, and our multimedia content. The GDrive of our dreams would be accessible from any computer, keeping in sync all our user data, preferences, and settings. You can see a hint of how this sync could work with the way the Google Chrome web browser stores your favorites. Your bookmarked sites are now available in the browser no matter what PC you use while a backup copy sits in Google Docs. GDrive should do the same, but not just for web browser favorites - for everything. That would be the final step for making a cloud OS a reality.

It's almost strange at this point that Google hasn't released something of the sort yet. In fact, they've let Microsoft beat them to the punch in this instance courtesy of Microsoft's SkyDrive service which launched back in early 2008. SkyDrive offers a free 25 GB of online storage for your files and also serves as the central repository for Windows Live Photos as well as the documents created via the new Office Web Applications service, Microsoft's challenge to Google Docs. But where's Google's answer to this? When will it come? Will it ever?

Perhaps the company is waiting for the release of Google Chrome OS to dazzle us with some sort of revamped interface for a game-changing cloud computing operating system. Or perhaps the company is just doing what it does best: offering solutions that are simply good enough.

Today, Google has announced a new feature of Maps that will allow users to find flu vaccines near them. In partnership with the U.S. Department of Health and Human Services, the American Lung Associaltion, and Flu.gov, Google Maps is now helping users search for seasonal flu vaccination locations, H1N1 flu shots, or both together.

Now, Google has gathered information about locations of flu vaccine shots from 20 states in the U.S. Google is also collecting information from chain pharmacies and other vaccine providers in all 50 states. Currently, users can find vaccine shots available from retail chains such as Walgreen's, CVS, Kmart, and WinnDixie.

The application gives vaccine location hours, when available, and even lets users know when vaccine supplies have run out at a particular location. All in all, it's a useful tool for quickly and simply finding the nearest place to get a flu shot.

For more information on how Flu Trends works, check out this video from Google.org:

It's not for everyone, but we talked to a variety of developers who are looking forward to kicking the tires. Below are opinions before launch from three developers we have a lot of respect for. Two are enthusiastic and one is skeptical.

Rob Pike also gave an hour-long talk about Go late last month.

Developer Reactions

GitHub Co-Founder Chris Wanstrath

I'm definitely on the lookout for C-like languages with good C integration and solid package support (for organization). Hopefully Go provides the former with its "syscall" package (or something similar) - building on existing libraries is a huge boon to young languages, as Scala and Clojure have shown with their Java integration.

Organizing big C projects is always a challenge, and borrowing packaging ideas from higher level languages like Python could really help.

Can't wait to see the site and play with a few examples.

Alex Iskold, founder and CEO of Adaptive Blue

Go appears to be procedural language, based on C/C++ syntax, skewed heavily towards C. It has C memory manipulation model with addresses and pointers, which is complicated and not used in Java, PHP, Ruby, etc.

There is nothing in this tutorial that attracts my eye, other than built-in parallel processing capability. C historically lacked threading (although current versions have it), but having it built in natively into the language is always great.

I am a fan of Java and Object-Orientation, so new procedural languages sound like a thing of the past to me.

If this is positioned as alternative to JavaScript, I do not see why this is necessary. Why not take JavaScript and make it better / add richer libraries like JQuery as part of the language. What Google has done with Gears for example, is built stuff using native C/C++ code and wrapped it into JavaScript calls - I think that is a better way to move forward and to make things faster.

Larry Price, Computer Systems Consultant

This is a very clean and powerful language. It's a direct descendant of C with elements of Haskell, OCaml, python and erlang visible as influences. It seems like yet another attempt to make a "better C than C", and from a first shallow glance it seems like a clear winner.

Objective-C fans (mac programmers) will probably sniff that it's nothing new, and that clean message passing semantics have been available to programmers for decades, but there are some deep differences; Go is not an object oriented language although you can use it in an objected oriented manner. In many respeccts Go is not a new language, it will seem very familiar to anyone who has used C or C descended languages; and most of the advanced features that it adds to C are implemented in other languages.

Go strikes a good balance between legibility, low-level functionality and high-level functional programming features. It will have a strong appeal to programmers who are interested in the type safety and concurrency friendly features of Haskell or erlang, but want to access them in a more familiar C-like syntax.

It has a good chance to make type-safe concurrent programming a mainstream choice.

What do you think?

In an interview today with Australian media outlet Sky News, Murdoch hinted that when News Corp sites start charging users for access to content around June 2010, said content will be de-indexed from all search engines. It's an old-school approach to the burgeoning threat of new media, but who wants to argue with a 78 year-old billionaire? And exactly how much share does News Corp hold in the search engine news v. old-guard media battle?

Murdoch continues to criticize Google as plagiarists who steal News Corp content, just as he claims users should never have had access to free content in the first place. Take a look at this video of the interview. Beware: It's long and deeply fascinating:

The most fascinating thing about the interview is that Murdoch points out the sticking points of traffic valuation and monetization that only a 4-billionaire has the right to comment on. Does inclusion in Google News results guarantee clickthroughs? Do clickthroughs guarantee loyal readership? Does loyal readership in any way convert to ad dollars?

Taking it a step further, when one considers the absolutely abysmal rates of conversion of clickthrough users on advertisers' websites, does the funnel of Google News traffic generate revenue from consumers to advertises and thence to publishers?

Or is it all a rhubarb goulash, as Murdoch would have it?

Clearly, there are subtleties to the case, which carries with it every complexity ever pondered by those who attempt to provide value to users - most of whom indignantly refuse to pay for content and accept pirated content as a substitute - and those who guard the economic and cultural longevity of traditional media, many outlets of which continue to provide the most valuable and insightful commentary in a news environment that revolves around instant deadlines, fast-beats-best reportage, and shoddy fact-checking.

But as much as the newsprint-and-ink old guarders among us can appreciate Murdoch's last stand, one appreciates - as a user and as a technologist - the cooperation and innovation of companies such as the New York Times, the BBC, and other very traditional news outlets that have seen the value of distribution, aggregation, and mass information.

If, however, News Corp decides to deny Google bots access to its content, Google news will likely suffer little. Between the Associated Press, Reuters, and other print and broadcast news services, one wonders how much the absence of News Corp listings - primarily represented by the Wall Street Journal and FOX - will affect Google News.

Annotation startup Reframe It, a 14-person team, claims that Google's hot new product Sidewiki crosses the line between competitive innovation and IP infringement. And with a few Googlers caught with their hands in Reframe It's cookie jar, there might be some validity to this claim.

Fast-forwarding to this fall, Google launched Sidewiki in September, almost a full year after the debut of Reframe It. Looking at these demo videos back-to-back, the similarities are obvious:

For an in-depth side-by-side comparison of both apps, see Google Watch's post on the subject. The basic conclusion is that the products look similar enough that Google's source code had better be drastically different from Reframe It's if they are to avoid a major lawsuit.

But if we had a nickel for every time we spotted disgraceful similarities between web products, we'd be... Well, never mind what we'd be doing with that stack o' nickels. Here's the interesting part: Reframe It CEO Bobby Fishkin, who claims his company has neither the time nor the resources to take on tech behemoth and pop culture darling Google, told eWEEK that there were several attempts to learn and assimilate his startup's technology and interface, right down to the icon designs.

According to eWEEK, Fishkin claims that one of his board members, Terry Winograd, sat in on a Google meeting in July 2008 and told a top Google exec to take a look at Reframe It. The as-yet unnamed Googler said the startup looked interesting and that the info would be passed along.

In the months that followed, at least six Reframe It accounts were registered to Google employees, which would allow engineers "plenty of time to explore every nook and cranny of our functionality," said Fishkin.

But the real kicker is Google's alleged attempt to hire Reframe It co-founder and lead engineer Ben Taitelbaum just days before Sidewiki launched.

And what was the official Google response to these reports?

"The variety of existing products in this space and the increasing number of sites that enable user generated content shows that there is growing demand for allowing users to contribute to the Web," a Google rep wrote to eWEEK in a measured but definite dismissal of Reframe It's claims.

Certainly, Google has been talking and thinking about annotation for years. And its end product has many differences from others on the market. And the market has a few notable competitors aside from Reframe It, all of which Google probably explored in due diligence processes. But if and when these two products face off in court, attorneys will be arguing whether the Google product - which, if only because it came after Reframe It's version, is without question a knockoff - is in actual violation of Reframe It's patents. And since Reframe It's patent application is still pending, they can amend the language to include Sidewiki's UX, technology, etc.

The situation is, indeed, fraught with run-of-the-mill, workaday, tech IP drama. And we look forward to following up on these reports accordingly.

The dashboard itself doesn't offer the ability to change any privacy settings. It links to the respective services' privacy pages where users can make changes.

Nothing New

It is true that, as Google puts it, the "scale and level of detail of the Dashboard is unprecedented" - Google never made something like this available before. The data that appears in the dashboard isn't really the data that Google is interested in, though. All Google really cares about is the data that it can use to show you better AdSense ads.

This Is It?

As the LA Times points out, Google's "data storage revolves around precisely how and what the company does to analyze and profit from user information." This would be interesting information to have, though it's also the data that Google is the least likely to share. Google also doesn't share information it collects about you through cookies, its server logs or its advertising programs.

It is good to see that Google makes it easier for users to see an overview of all the data they have given to Google and made public. Maybe it will come as a surprise to some people that Google knows what emails they have received and that the company keeps track of all the YouTube videos they have watched. For most users, though, the dashboard won't offer any major revelations.

The tech sector is subjected to the same indignities, beginning with a new enterprise search product from our friends at Google, who insist that users will stay on your pathetic website for about eight seconds unless they find exactly what they're looking for. And how ever shall they find it? Google Commerce Search, of course!

Here's a prematurely festive and depressingly commercial demo video:

Sure, it'll make users happier by decreasing the keystrokes between rabid greediness and commercial satiety, but at what cost? That's a factor you'll have to contact Google to actually learn about; pricing is not available online.

It's dirty electronic retailer ROI powered by Google - happy holidays. Webinars are coming to a monitor near you on November 12, November 17, and December 3.

According to Google's blog post about the beta release, the sync feature has to first be activated on each of your computers where Google Chrome is used. To do this, you'll need to download the beta build of the browser available here. Once installed, click the "wrench" menu (yes, the one with the wrench icon) in Google Chrome and select "Synchronize my bookmarks" from the menu that appears. Sign into your Google account in the dialog box that pops up. If you've already set up Sync on another computer, you'll then be prompted to confirm that your different sets of bookmarks should be merged together. In that case, click "Merge and Sync" to complete the process. Finally, click "OK" when you've finished.

Not only does this feature sync your bookmarks, it also creates a copy of your bookmarks file on Google Docs in a new folder called "Google Chrome." (Wonder what else will go in that folder in the future?)

What's in Store for Sync

For now, the Sync feature is only synchronizing browser bookmarks, but the framework behind Sync is ultimately designed to handle the synchronization of other kinds of browser data as well. As to what sort of data that could be, Google can't provide any official confirmation just yet. However, they did say that you could imagine that "this type of infrastructure could be extended to other types of user data such as passwords" in the future. We'll speculate that it will eventually include those passwords, your browser history, and whatever favorite websites appear as thumbnails on the New Tab page. After all, if Mozilla's Weave Sync prototype can handle those sorts of tasks already, there's no reason to believe that Google couldn't do the same.

Because the new Sync feature uses an XMPP connection to synchronize the changes, changes made on one computer are synchronized immediately to another. Not just quickly, mind you, but immediately. This is possible because XMPP is what's known as a "real-time" communication protocol - the same one that powers Google Talk, the company's IM service.

The use of this sort of technology hints at how Google plans to make their Chrome web browser the core of their upcoming netbook operating system, Google Chrome OS. The new OS will run web applications "in the cloud," a radical change from current OS offerings where many applications are still installed on the computer's hard drive itself. With Chrome (the browser's) ability to synchronize data in real-time between computers, it's easy to see how a cloud OS could operate. It wouldn't matter which machine you used, your data would be available, stored in the cloud, synchronized, and all accessible upon login to your Google account. That prospect is either amazing or terrifying depending on your trust level when it comes to Google. Perhaps it's even both. 

Chrome Gets Faster, Too

While Bookmark Sync is the most interesting feature to debut in the new beta, there are some notable speed improvements to mention, too. The latest build improves performance by 30% since the current stable release of Chrome and by 400% since the very first stable release, as measured by Mozilla's Dromeao DOM Core Tests. 

As noted earlier, speed was a major factor in Firefox's 3.6 beta 1, released just this Friday. Both companies are going head-to-head when it comes to browser speed, JavaScript performance and startup times, but no official speed tests have been done yet to compare the two new beta releases.

To download the latest build of Google Chrome beta, head over to the Chrome beta site here. The official beta requires Windows XP SP2 or higher.