Saturday, January 8, 2011

[Gd] Beta Update

| More

Google Chrome Releases: Beta Update

The Beta channel has been updated to 9.0.597.45 for Windows, Linux and Chrome Frame.

Flash Player sandboxing has been restored, and accelerated composting and WebGL have been moved behind flags temporarily: --enable-accelerated-compositing and --enable-webgl respectively.

If you find new issues, please let us know by filing a bug at

Anthony Laforge
Google Chrome

[Gd] New Year's Resolutions

| More

Google Testing Blog: New Year's Resolutions

By James Whittaker

I know many people who laugh at the concept of resolutions, easily made and easily broken. All true. However, I am a runner now because of a resolution I made about a decade ago and my personality has undergone a successful renovation or two over the years as well. When they stick, resolutions can become habits and the emergence of the occasional butterfly makes them a worthwhile exercise. With the optimism of a new year, I present my Google Testing resolutions for 2011 which I hereby declare the Year of the User.

1. I will listen to users more and developers less.

Developers, by definition, are engineers lost in the details of implementation. When it comes to testing concerns, such implementation details clog a tester's neural pathways with issues that simply should not be relevant. I resolve to take the high road as often as possible and consider user scenarios, integration issues and end-to-end uses of the system above all other concerns. And, yes, that will mean telling developers "sorry, dude, your broken build simply is not my concern."

2. I will push all implementation testing issues to developers.

My first resolution may lead readers to believe that testing implementation details isn't important. Let me be clear. Testing implementation details is important. When they go untested they create enough noise that user-oriented testing is compromised by the constant emergence of silly bugs. Silly bugs mask important ones. Find them at the source: ensure that proper unit testing and automated smoke tests are present and owned by the people most qualified to write and maintain them: developers. I resolve not to be sidetracked by silly bugs but to push back hard on the developers who are happy to write the bug but neglect to write the test for it.

3. I will endeavor to tie together all user-oriented testing.

In the run up to releasing Chrome OS for pilot last year it was clear that many of the bugs found during dogfood (internal testing), crowd-sourced and out-sourced testing had already been found by my test team. Not only is there is a lot of repetitive and wasteful testing being performed, my team isn't getting enough credit for finding these important issues early. I resolve to introduce technology that will allow all testers to share testing tactics and see each other's work, ultimately erasing the boundaries between these common phases and allowing testers who join a project late to build upon the work of those who've been there for a while.

Finally, I resolve to expose more information about how Google tests internally. I am going to return to the conference circuit this year and talk frankly about what we are doing, the good, the bad and the downright embarrassing in the hopes that other testers at other companies do the same. I am also going to push more Google testers to post their experiences on this blog and join me at industry events to discuss these things with anyone struggling with the same issues.

Happy New Year! May it be one that sees a higher level of quality from every corner of our industry.

Friday, January 7, 2011

[Gd] BigQuery, meet Google Spreadsheets

| More

Google Code Blog: BigQuery, meet Google Spreadsheets

Since announcing BigQuery at Google IO last May, we’ve been very excited by the response and feedback we’ve received from the developer community, enterprises and academia. The one consistent request we heard from everyone is the ability to interactively analyze large volumes of data without having to worry about provisioning, maintaining and scaling infrastructure.

Today, we would like to announce the integration of BigQuery with Google Apps Script and Google Spreadsheets, a feature we first demoed at Google IO. With this integration users now have the power to query multi-billion row tables, visualize the results and share them with others. Below you can see a simple script that queries a sample dataset and plots the results. A simple tutorial is available here with more to come soon.

We’ve seen a big uptake of the APIs (released in October) which let you create, populate and delete tables in BigQuery. Users have been loading more and more data in BigQuery. For instance the current M-Lab dataset in BigQuery stands at 240B rows!

The details of BigQuery and new features are available on the BigQuery website. We are gradually adding more developers during this free preview period. Please sign up for an invitation, and let us know about the creative and valuable ways you’re using BigQuery.

By Amit Agarwal, BigQuery Team

Thursday, January 6, 2011

[Gd] Dev mode plugin now available for 64-bit IE

| More

Google Web Toolkit Blog: Dev mode plugin now available for 64-bit IE

The GWT development mode plugin is now available for the 64-bit version of Internet Explorer. You can download it as usual when prompted to do so by the "missing plugin" page.

Note that this is unrelated to the IE9 issue previously discussed on this blog. The GWT team is still working with Microsoft on a fix.

[Gd] Happy New Year, OpenSocial!!

| More

OpenSocial API Blog: Happy New Year, OpenSocial!!

I'd like to congratulate the OpenSocial community on an incredible 2010! Even though it seemd to fly by, it's worth taking a quick look back at all the things, that, as a community, we were able to accomplish in 2010.

Not just one release, but two!
In 2010, we published OpenSocial 1.0, which represented a significant step in maturing and stabilizing the specification and programming model. In November, 1.1 was released. This included new capabilities for inter-gadget communication (pub/sub), which is a major requirement for enterprise vendors who are adopting OpenSocial. 1.1 also included the first extension--the OpenSocial WAP Specification.

New Board Members & Officers
During 2010, the Board of Directors appointed a completely new set of officers. One of the telltale signs of a strong and vibrant organization, especially one that consists of volunteers, is it's ability to gracefully handle change. Kudos to the OpenSocial Board and Officers (present company excepted) for handling this with grace and professionalism. During this transition, IBM and Jive Software joined OpenSocial's Board. Because they are Corporate Designators, these companies, along with the three founding members, Yahoo!, Google, and MySpace, have made a financial commitment to OpenSocial. Combined with their excellent technical resources that work on advancing the specification and, in many cases, open source code, OpenSocial is positioned to remain a key Internet technology for years to come.

Your Vote, Your Voice 2010
In 2010, we had privilege of electing two Community representatives, Paul Lindner and Mark Halvorson, to OpenSocial's Board. Both of these gentlemen continue to set the bar very high for their commitment to OpenSocial and involvement in our community. Paul's leadership of Apache Shindig ensures that there is a proven, open source implementation of OpenSocial available to all. Mark Halvorson has worked to get our Web presence organized by working with Atlassian to host OpenSocial's new Wiki. While we are not quite done migrating this over yet, this is a significant step forward for the community as it provides a more secure and stable infrastructure. Thanks to both Paul and Mark for all of their hard work in 2010.

Can you say OpenSocial in three languages?
Thanks to Shindig, OpenSocial has long been available in PHP and Java. In 2010, MySpace announced plans to contribute a significant portion of their .Net infrastructure to open source. This will provide another implementation language for OpenSocial and, hopefully, will open up an avenue for a new set of developers. Way to go MySpace!

The year of the enterprise
In 2008, OpenSocial exploded in popularity and adoption in consumer facing social networks. In 2010, a similar explosion occurred among enterprise vendors. The year started with the publication of the Enterprise OpenSocial Whitepaper. At Google IO, Atlassian, Cisco, IBM, and Jive Software, presented a technical session on how OpenSocial is a key underlying technology in their Enterprise offerings. The year culminated with the first ever Enterprise Interop event. Participants from Appirio, Atlassian, Cisco, IBM, Jive Software, Magento, Oracle, PayPal, SAP and others worked together to get a variety of applications running on multiple containers. While this event illustrated to us that we still have work to do to attain the interoperability that we want, overall, it was a huge success. We were able to demonstrate several applications running in multiple containers unchanged. More importantly, we were able to continue the momentum in collectively proving OpenSocial ready for the Enterprise.

Growing our community
One of the great things about an open community is getting the opportunity to work with a diverse set of people across a broad spectrum of industries. There's literally no limit to the energy and ideas that come from working together. This was no more evident than in two great community events this year, the OpenSocial State of the Union, and the OpenSocial Europe/OpenSocial in Education Summit. Thank you again to MySpace and SURFnet for organizing and hosting these events.

Welcome 2011!
With a year like 2010 behind us, it would be easy to sit back and relax. Hardly! Work is already underway defining and implementing OpenSocial 2.0. We've got an aggressive schedule and are targeting to have an implementor's draft at the end of Q1/2011.

If 2010 was "the year of the Enterprise", we've got to make 2011 "the year of interop". Collectively, we'll need to improve interoperability of OpenSocial applications. Part of this will be continuing to mature the specification, but it will also mean more interoperability events--and opportunities for you to get involved.

Your Vote, Your Voice: 2011
Finally, this is a reminder that we'll start 2011 off with elections for the Community Representative to the OpenSocial Foundation Board of Directors. Nominations are open until January 9th.

Given there's been so much accomplished in 2010, I'm sure I've failed to mention something. I guess that's what comments & replies are for! While I couldn't possibly name everyone that's working hard to make OpenSocial a success, on behalf of the OpenSocial Foundation, and the Community--Thank you, and congratulations on a great 2010!

Mark Weitzel, President, OpenSocial Foundation
The Web is better when it's OpenSocial!

[Gd] Dev Channel Update

| More

Google Chrome Releases: Dev Channel Update

Update: 1/5 10pm PST, the dev channel has now been updated to 10.0.628.0 for Windows as well.

The Dev channel has been updated to 10.0.628.0 for Linux

This release fixes several crashes and small issues:

  • Updated V8 -
  • Updated WebKit - 534.16
  • Eliminated crash on shutdown after “Clear All Downloads” (Issue 66676)
Known Issues
  • NaCl SDK - Apps are not working (Issue 62570)

More details about additional changes are available in the log of all revisions.

You can find out about getting on the Dev channel here:

If you find new issues, please let us know by filing a bug at

Karen Grunberg
Google Chrome

[Gd] Beta Channel Update

| More

Google Chrome Releases: Beta Channel Update

The Beta channel has been updated to 9.0.597.44 for Windows, Mac, Linux and Chrome Frame.

Flash Player sandboxing has been temporarily moved behind a flag --enable-flash-sandbox.

If you find new issues, please let us know by filing a bug at

Anthony Laforge
Google Chrome

[Gd] Beta Channel Update

| More

Google Chrome Releases: Beta Channel Update

The Beta channel has been updated to 9.0.597.42 for Windows, Mac, Linux and Chrome Frame.

More details about additional changes are available in the svn log of all revision.

If you find new issues, please let us know by filing a bug at

Anthony Laforge
Google Chrome

Wednesday, January 5, 2011

[Gd] Announcing the High Replication Datastore for App Engine

| More

Google App Engine Blog: Announcing the High Replication Datastore for App Engine

When App Engine launched over two years ago, we offered a Datastore that was designed for quick, strongly consistent reads. It was based on a Master/Slave replication topology, designed for fast writes while still allowing applications to see data immediately after it was written. For the past six months, as you are probably aware, we’ve been struggling with some reliability issues with the App Engine Datastore. Over the course of the past few months, we’ve made major strides in fixing these issues. However, our experience with these issues has made us rethink some of our design assumptions. As we promised you in some of our outage reports earlier this year, we wanted to give you a more fundamental solution to the problem.

Today I’m proud to announce the availability of a new Datastore configuration option, the High Replication Datastore. The High Replication Datastore provides the highest level of availability for your reads and writes, at the cost of increased latency for writes and changes in consistency guarantees in the API. The High Replication Datastore increases the number of data centers that maintain replicas of your data by using the Paxos algorithm to synchronize that data across datacenters in real time. One of the most significant benefits is that all functionality of your application will remain fully available during planned maintenance periods, as well as during most unplanned infrastructure issues. A more detailed comparison between these two options is available in our documentation.

From now on, when creating a new application, you will be able to select the Datastore configuration for your application. While the current Datastore configuration default remains Master/Slave, this may change in the future.

Datastore configuration options when creating an app.

The datastore configuration option can not be changed once an application is created, and all existing applications today are using the Master/Slave configuration. To help existing apps migrate their data to an app using the High Replication Datastore, we are providing some migration tools to assist you. First, we have introduced an option in the Admin Console that allows an application to serve in read-only mode so that the data may be reliably copied between apps. Secondly, we are providing a migration tool with the Python SDK that allows you to copy from one app to another. Directions on how to use this tool for Python and Java apps is documented here.

Now, a word on pricing: Because the amount of data replication significantly increases with the High Replication datastore, the price of this datastore configuration is different. But because we believe that this new configuration offers a significantly improved experience for some applications, we wanted to make it available to you as soon as possible, even though we haven’t finalized the pricing details. Thus, we are releasing the High Replication Datastore with introductory pricing of 3x that of the Master/Slave Datastore until the end of July 2011. After July, we expect that pricing of this feature will change. We’ll let you know more about the pricing details as soon as they are available, and remember, you are always protected when pricing changes occur by our Terms of Service. Due to the higher cost, we thus recommend the High Replication Datastore primarily for those developers building critical applications on App Engine who want the highest possible level of availability for their application.

Thank you, everyone, for all the work you’ve put into building applications on App Engine for the past two years. We’re excited to have High Replication Datastore as the first of many exciting launches in the new year, and hope you’re excited about the other things we’ve got in store for App Engine in 2011.

Posted by Kevin Gibbs, The App Engine Team