The performance bar for all three versions keeps getting higher: today’s new stable release for Windows, Mac and Linux is our fastest yet, incorporating one of our most significant speed improvements to date. We’ve improved by 213 percent and 305 percent in Javascript performance by the V8 and SunSpider benchmarks since our very first beta, back in Chrome’s Cretaceous period (September 2008). To mark these speed improvements, we’ve also released a series of three unconventional speed tests for the browser:
(If you’re interested in how we pitted Chrome against the forces of a potato gun, lightning, and the speed of sound, take a look behind-the-scenes in this video, or read the full technical details in the video’s description drop-down in YouTube).
You may also notice that today’s new stable release comes with a few new features, including the ability to synchronize browser preferences across computers, new HTML5 capabilities and a revamped bookmark manager. For more details, read on in the Google Chrome Blog.
If you haven't tried Google Chrome since the stone age, check out this brand new stable release. If you're already using Chrome, you'll be automatically updated to this new version soon. To try it right away, download the latest version at google.com/chrome.
(First dev, then beta, now stable! Many thanks to Christoph Niemann)
Posted by Brian Rakowski, Product Manager, Google Chrome
In 1978, people told Douglas Twiddy he was crazy when he started renting out vacation homes in the Outer Banks of North Carolina. More than 30 years later, his son Ross is using our AdWords advertising program to help attract prospective renters — and grow his small business, Twiddy. Thanks in part to AdWords, in just the past two years the company has added 100 new homes to its listings and hired 16 full-time employees, and it brings on another 50 seasonal employees each year.
This week is National Small Business Week, and Ross will be with me on Capitol Hill in Washington today to share his story and help unveil something that means a tremendous amount to me: a new report detailing, for the first time ever, Google’s economic impact in all 50 states.
People think of Google first and foremost as a search engine, but it’s also an engine of economic growth. In our report, we’re announcing that in 2009 we generated a total of $54 billion of economic activity for American businesses, website publishers and non-profits. Over the years people have asked us whether we could quantify our economic impact on a state level, and we’re pleased to do that for the first time with this report, which you can download at google.com/economicimpact.
In a time of tighter budgets and a slow economic recovery, we’re glad to support so many small businesses and entrepreneurs across the country by helping them find new customers more efficiently and monetize their websites through targeted advertising.
Here’s a video from me and our Chief Economist, Hal Varian, with more background on where we get the numbers:
The report is filled with really wonderful stories about the direct economic impact that AdWords, AdSense, Google Grants and our search engine have across the country. These are the stories of entrepreneurs across the country growing their businesses with Google. And this morning Googlers are hosting events in 10 other cities across the country (Atlanta, Austin, Boston, Chicago, Detroit, New York, Oakland, Portland (OR), Raleigh and Seattle) to help share those stories. Ladies and gentlemen, start your economic engines!
Posted by Claire Hughes Johnson, Vice President, Global Online Sales
Category #3: Secret Change Agent: making our world a better place through innovative change
Runner-ups ($1,000 each) Xiangbo Meng (Plant Sciences), age 17, Beijing, China Aqueous Extract of Lemon Leaves as a Novel Powerful Insecticide Against Trialeurodes Vaporariorum (Whitefly)
Sonia Rao (Microbiology), age 17, Missouri Bacterial Silencing: The Discovery of Quorum Quenching Soil Microbes for the Development of Antimicrobial Compounds
Winners ($10,000 each) William Lopes (Microbiology), age 20, Brasil Utilization of the Fungus Aspergillus Niger on Wastewater Treatment II
Karoline Elis Lopes Martins (Environmental Management), age 18, Brasil Construction of a Continuous Flow SODIS system with PET Bottles Integrated to a Water and Waste-Water Treatment System
For a full listing of the Intel ISEF Grand Award and Special Award winners, visit the Intel ISEF 2010 homepage here.
Posted by Dolores Bernardo, Talent & Outreach Programs Manager
It is estimated that at least 6 million gallons of oil have leaked into the Gulf of Mexico since the Deepwater Horizon explosion a month ago. Cleanup efforts are underway, but the oil has spread extensively around the Gulf and along the southern U.S. coastline. Oil has begun washing up on the beaches of Louisiana and the delicate wetlands along the Mississippi River, and can spread to Florida and throughout the Gulf as weather conditions change. This sequence of images, coming from NASA’s MODIS satellites, illustrates the movement and growth of the oil slick over the past few weeks:
April 25, 2010
April 29, 2010
May 9, 2010
May 17, 2010
The last image, taken earlier this week (on May 17), shows the coastal areas currently at risk from the spreading oil, and can help those working on the wide range of relief efforts.
You can view this and other MODIS imagery in Google Earth by downloading this KML. You can also view additional imagery and find other resources and news at our oil spill crisis response page.
PAC-MAN seems like a natural fit for the Google homepage. They’re both deceptively straightforward, carefully hiding their complexity under the hood. There’s a light-hearted, human touch to both of them. And we can only hope you find using Google at least a quarter as enjoyable as eating dots and chasing ghosts. You know, without actually needing any quarters.
Posted by Marcin Wichary, senior UX designer and developer
On Friday May 14 the Irish Data Protection Authority asked us to delete the payload data we collected in error in Ireland. We can confirm that all data identified as being from Ireland was deleted over the weekend in the presence of an independent third party. We are reaching out to Data Protection Authorities in the other relevant countries about how to dispose of the remaining data as quickly as possible.
You can read the letter from the independent third party, confirming deletion, here.
[original post]
Nine days ago the data protection authority (DPA) in Hamburg, Germany asked to audit the WiFi data that our Street View cars collect for use in location-based products like Google Maps for mobile, which enables people to find local restaurants or get directions. His request prompted us to re-examine everything we have been collecting, and during our review we discovered that a statement made in a blog post on April 27 was incorrect.
In that blog post, and in a technical note sent to data protection authorities the same day, we said that while Google did collect publicly broadcast SSID information (the WiFi network name) and MAC addresses (the unique number given to a device like a WiFi router) using Street View cars, we did not collect payload data (information sent over the network). But it’s now clear that we have been mistakenly collecting samples of payload data from open (i.e. non-password-protected) WiFi networks, even though we never used that data in any Google products.
However, we will typically have collected only fragments of payload data because: our cars are on the move; someone would need to be using the network as a car passed by; and our in-car WiFi equipment automatically changes channels roughly five times a second. In addition, we did not collect information traveling over secure, password-protected WiFi networks.
So how did this happen? Quite simply, it was a mistake. In 2006 an engineer working on an experimental WiFi project wrote a piece of code that sampled all categories of publicly broadcast WiFi data. A year later, when our mobile team started a project to collect basic WiFi network data like SSID information and MAC addresses using Google’s Street View cars, they included that code in their software—although the project leaders did not want, and had no intention of using, payload data.
As soon as we became aware of this problem, we grounded our Street View cars and segregated the data on our network, which we then disconnected to make it inaccessible. We want to delete this data as soon as possible, and are currently reaching out to regulators in the relevant countries about how to quickly dispose of it.
Maintaining people’s trust is crucial to everything we do, and in this case we fell short. So we will be:
Asking a third party to review the software at issue, how it worked and what data it gathered, as well as to confirm that we deleted the data appropriately; and
Internally reviewing our procedures to ensure that our controls are sufficiently robust to address these kinds of problems in the future.
In addition, given the concerns raised, we have decided that it’s best to stop our Street View cars collecting WiFi network data entirely.
This incident highlights just how publicly accessible open, non-password-protected WiFi networks are today. Earlier this year, we encrypted Gmail for all our users, and next week we will start offering an encrypted version of Google Search. For other services users can check that pages are encrypted by looking to see whether the URL begins with “https”, rather than just “http”; browsers will generally show a lock icon when the connection is secure. For more information about how to password-protect your network, read this.
The engineering team at Google works hard to earn your trust—and we are acutely aware that we failed badly here. We are profoundly sorry for this error and are determined to learn all the lessons we can from our mistake.
Posted by Alan Eustace, Senior VP, Engineering & Research
Google Chrome for Linux
Follow
