Delivering Breaking news

There’s no way I could deliver breaking news, I would feel like bringing potential lies to people. That’s what happened in the last two days with Google Chrome and that’s why I waited a before writing a little something about it. We’ll have a look at the common myths together.

Google want rights to things you do using Chrome

This little thing from the Google Chrome’s EULA was raised today:

By submitting, posting or displaying the content you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through, the Services. This license is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.

This is scary isn’t it? Google is getting the rights to everything I post through their browser. What a luck I’m writing this post in Firefox! Instead of believing it without double checking this information, I visited Matt Cutts’ blog (http://www.mattcutts.com/blog/). Matt Cutts is the head of Google’s Webspam team so he really knows what he’s talking about and here’s what he posted today:

I knew that Google didn’t want to assert rights on what people did using Google Chrome, so I asked the Chrome team and Google lawyers for their reaction or to clarify (probably several other people pinged them too). Here’s what I heard back from Rebecca Ward, the Senior Product Counsel for Google Chrome:

“In order to keep things simple for our users, we try to use the same set of legal terms (our Universal Terms of Service) for many of our products. Sometimes, as in the case of Google Chrome, this means that the legal terms for a specific product may include terms that don’t apply well to the use of that product. We are working quickly to remove language from Section 11 of the current Google Chrome terms of service. This change will apply retroactively to all users who have downloaded Google Chrome.”

Ok, and l checked the EULA tonight and it looks like this now:

11. Content license from you

11.1 You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services.

A lot less scary isn’t it? Issue resolved, next!

Another browser to support!

Again, Matt Cutts the Google hero answered this:

Q: Another browser? Geez, I’m a webmaster/search engine optimizer/front-end programmer and I don’t want to worry about another browser.
A: Google did not add another rendering engine. Google Chrome uses WebKit for rendering, which is the same rendering engine as Apple’s Safari browser, so if your site is compatible with Safari it should work great in Chrome. Personally, I do think creating clean code that validates and works on many different browsers will be an important skill for webmasters and web designers. These days a smart site owner thinks about how their web site looks to all browsers, from Internet Explorer to Safari to Opera to an iPhone.

So, just ensure your website looks fine on Safari and you should be fine!

Other general issues

For other general issues about Google Chrome, visit the following two posts on Matt’s blog:

http://www.mattcutts.com/blog/common-google-chrome-objections/

http://www.mattcutts.com/blog/google-chrome-communication/

My general appreciation of Chrome

I personally love it. OK, there’s a lack of features, but the thing is lightning fast. I’m a big fan of Opera and I’m pretty sure this little thing is faster. I hate the fact that there’s no status bar, no rss icon in the URL bar and no extension support, but that will come for sure. I will still continue to use Firefox because it offers so much to web developers: toolbars, firebug, etc, but I will also use Chrome because it feels lighter and is much faster.