Wednesday, September 3rd, 2008

Audible Ajax Episode 28: The State of Ajax, with Chrome and friends

Category: Podcasts

<>p>

Everyone knows that the big news of the week is Google Chrome, Chromium, and V8. Ben and I sat down for our podcast update and delve deeper at how all of the browsers are doing interesting things and progressing nicely. We discuss SquirrelFish, TraceMonkey, and of course V8.

We also delve into Canvas land and the fun and frolics that are planned for The Ajax Experience in Boston that happens soon. I am excited about the framework mini-events that happen around the same time too, and gather the crew behind jQuery, Dojo, and Prototype.

We have the audio directly available, or you can subscribe to the podcast.

Related Content:

Posted by Dion Almaer at 8:58 am
5 Comments

+++--
3.7 rating from 27 votes

5 Comments »

Comments feed TrackBack URI

Hi there,
I’ve been trying Chrome for a while today and I must say I’m pretty impressed.
I believe Google is really up to something with this. I just have a little worry. When I Installed Chrome it is the first time i read the terms and conditions. Usually i can’t bother and just say “Yeah! yeah! fine! fine! click!”. By profession I’m a web/graphic designer and i got scared by this:

11. Content licence from you

11.1 You retain copyright and any other rights that you already hold in Content that you submit, post or display on or through the Services. By submitting, posting or displaying the content, you give Google a perpetual, irrevocable, worldwide, royalty-free and non-exclusive licence to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content that you submit, post or display on or through the Services. This licence 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.

11.2 You agree that this licence includes a right for Google to make such Content available to other companies, organisations or individuals with whom Google has relationships for the provision of syndicated services and to use such Content in connection with the provision of those services.

11.3 You understand that Google, in performing the required technical steps to provide the Services to our users, may (a) transmit or distribute your Content over various public networks and in various media; and (b) make such changes to your Content as are necessary to conform and adapt that Content to the technical requirements of connecting networks, devices, services or media. You agree that this licence shall permit Google to take these actions.

11.4 You confirm and warrant to Google that you have all the rights, power and authority necessary to grant the above licence.

I do find it a bit scary, i know it is not completely relevant to the post, but in some way….

Read the small print…

Comment by zapatoche — September 3, 2008

I wrote some words about the importance of following Open Standards just for cases like this here; http://ra-ajax.org/google-chrome-ajax-the-open-web-and-open-standards.blog
@zapatoche
Does the LGPL which WebKit is built on really allow creating such licenses in derived works…?
If they do what they say they will do which is to also Open Source license the browser then I assume whatever Open Source license they choose to distribute it within must stop such EULA claims. Otherwise it is *not* Open Source. At least not the Source Code version of it which can be rebuilt and created a new installer for. I also suspect that with such an EULA the project will be *instantly* forked from regardless of what license they’re using, though assuming it’s an OSI approved license…

Comment by ThomasHansen — September 3, 2008

aaah… good ol’ scary google’s licences!..

Comment by mare — September 3, 2008

This has got to be the most ridiculous license in the history of ridiculous EULA’s. You should read this post before even considering using Chrome: http://tapthehive.s483.sureserver.com/chrome.html

Comment by Tavs — September 3, 2008

At first I was wondering why Google didn’t just work more closely together with Mozilla and FF. But after reading more about Chrome, I really like a lot of the ideas they are moving forward on. Also, I think both Google and Firefox will push the envelope and push each other with regards to the browser as an improved application platform. All of this will not only push MSFT, but innovation will continue to flow into WebKit from this other source. See this as all very positive for the user, and developers alike. (as an aside, the cartoon piece of communication was excellent, and more engaging than the typical release for sure).
Many thanks for the inspiring work.

Comment by holts — September 5, 2008

Leave a comment

You must be logged in to post a comment.