<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Webstock 2009 - ReadWriteWeb</title>
      <link>http://www.readwriteweb.com/archives/webstock-2009/</link>
      <description>Webstock 2009 on ReadWriteWeb</description>
      <language>en</language>
      <copyright>Copyright 2009 Richard MacManus</copyright>
      <managingEditor>readwriteweb@gmail.com</managingEditor>
      <lastBuildDate>Thu, 19 Feb 2009 17:07:30 -0800</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=4.23-en</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

      
      <item>
         <title>Ben Goodger on Google Chrome</title>
		<description><![CDATA[<p><img src="http://www.readwriteweb.com/images/chromologo2.jpg" /><a href="http://www.bengoodger.com/">Ben Goodger</a>, who leads the UI team of <a href="http://www.google.com/chrome">Google Chrome</a>, presented today at the <a href="http://www.webstock.org.nz/">Webstock</a> conference about browsers. He said that Google decided to build Chrome simply because &quot;browsers suck&quot;. Existing browsers were too slow (especially with javascript heavy apps), there are too many crashes, too easy to get pwned (security issues), and UIs were becoming more and more bloated. He said that Google has a history of improving on browsers and creating add-ons - including contributing to Mozilla's Firefox, where Goodger used to work before Google. But Google wanted to re-architect the browser and do something more ambitious than current browsers, including Firefox. </p>
]]>
<![CDATA[<p align="right"><em>Sponsor</em><br /><a href='http://d1.openx.org/ck.php?n=13934&amp;cb=13934' target='_blank'><img src='http://d1.openx.org/avw.php?zoneid=11205&amp;cb=13934&amp;n=13934' border='0' alt='' align="right" /></a></p>]]>

<![CDATA[<p>One of Chrome's innovations is to isolate and &quot;pre-emptively multi-task&quot; applications, just like operating systems do. This provides high performance, stability and security. So Google created the feature which has perhaps been Chrome's distinguishing one so far - enabling tab processes to function independently, so if one tab crashes the rest stay operational. Plugins also have their own processes, so that too provides more stability. Goodger referred to this as a &quot;jail cell for web content&quot;, preventing people from exploiting security issues in the browser.</p>
<p>Google also found that this independence of processes resulted in less &quot;jank&quot;, which is Google's term for unresponsiveness in the browser. Google wanted Chrome to be the &quot;fastest and least janky browser around." 200 miliseconds is their baseline for performance in startup speed, page load time, javascript execution. Responsiveness matters, said Goodger. He said that the user must always be in control of their browsing experience. As a sidenote, Goodger mentioned that the latest version of Internet Explorer 8 also now has the separate processing for different tabs feature.</p>
<p>Goodger talked about the user interface that Chrome has, which he said is a bit different from other browsers. He said they &quot;stripped down the UI&quot; and focused on the mantra &quot;content not chrome&quot;, which he acknowledged was ironic given the browser's name. He showed the following video, from Japan, to illustrate this approach:</p>
<p><object width="480" height="295"><param name="movie" value="http://www.youtube.com/v/SHZFsJKlsuA&hl=en&fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/SHZFsJKlsuA&hl=en&fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="295"></embed></object></p>
<p>There are obvious differences in the UI in Chrome, for example the lack of menu buttons. There are also other subtle differences, such as fewer &quot;attention-grabbing&quot; popups. Goodger also noted that Chrome has &quot;fewer options, better defaults&quot;. His rule is that &quot;options are never an excuse for bad design&quot;.</p>
<p>Goodger talked a little about Chrome's release cycle. Google uses channels to release versions of Chrome: stable, beta and dev (bleeding edge). Google aims to treat Chrome just like any web app, that releases early and often and in an automated method. So users get automated updates to the latest stable version, without having to manually update anything.</p>
<p>Finally Goodger reiterated that Google Chrome is open source, with community discussions happening at <a href="http://dev.chromium.org/">dev.chromium.org</a>.</p>
]]>
<![CDATA[<strong><a href="http://www.readwriteweb.com/archives/ben_goodger_on_google_chrome.php#comments-open">Discuss</a></strong>]]>

</description>
         <link>http://www.readwriteweb.com/archives/ben_goodger_on_google_chrome.php</link>
         <guid>http://www.readwriteweb.com/archives/ben_goodger_on_google_chrome.php</guid>
         <category>Browsers</category>
         <pubDate>Thu, 19 Feb 2009 17:07:30 -0800</pubDate>
<author>Richard MacManus</author>
      </item>
      
      <item>
         <title>Webstock 2009</title>
		<description><![CDATA[<p><img src="http://www.readwriteweb.com/images/webstock-09-banner.jpg" /><a href="http://www.webstock.org.nz/">Webstock</a>, a conference for Web professionals, is happening in Wellington New Zealand this week. As usual it's a classy lineup of speakers and a number of international webheads will be jetting in for the event. They include  science fiction author  Bruce Sterling,  Flickr's Heather Champ, Social Web designer Joshua Porter, Dopplr's Matt Biddulph, Institute for the Future's Jane McGonigal, Six Apart's David Recordon, The Guardian's Meg Pickard, NZ Foo Camp's Nat Torkington, Yahoo's Tom Coates, online performance artist Ze Frank, and many more.</p>]]>
<![CDATA[<p align="right"><em>Sponsor</em><br /><a href='http://d1.openx.org/ck.php?n=13882&amp;cb=13882' target='_blank'><img src='http://d1.openx.org/avw.php?zoneid=11205&amp;cb=13882&amp;n=13882' border='0' alt='' align="right" /></a></p>]]>

<![CDATA[<p>Webstock focuses mostly on web design topics, but in past years we've seen many great discussions on a variety of Internet issues. In 2006 the <a href="http://www.readwriteweb.com/archives/firefox_vs_ie_s.php">heads of Firefox and Microsoft's Internet Explorer</a> presented updates about their competing products. And a highlight for me last year was <a href="http://www.readwriteweb.com/archives/tom_coates_web_of_data.php">Tom Coates' talk on the Web of Data</a>.</p>

<p>As a resident of Wellington, I don't have far to go to attend Webstock. Some of the sessions I'm looking forward to checking out include David Recordon on the 'Open Social Web', Fiona Romeo on 'Astrotagging bots and citizen scientists' (got to attend that for the title alone!), Heather Champ on 'Shepherding Passionate Communities', and Google Chrome impresario Ben Goodger on 'A retrospective of ballet classics' (witty titles galore in Webstock this year). </p>
<p>Also who can resist Bruce Sterling's talk entitled 'The Short but Glorious Life of Web 2.0, And What Comes Afterward' (!)</p>
<p>If you're local and want to attend, you can still <a href="http://www.webstock.org.nz/09/pricing/">pick up a ticket</a>. It runs from  19-20 February, with workshops happening earlier in the week. If you can't attend, stay tuned for coverage on ReadWriteWeb later this week.</p>]]>
<![CDATA[<strong><a href="http://www.readwriteweb.com/archives/webstock_2009.php#comments-open">Discuss</a></strong>]]>

</description>
         <link>http://www.readwriteweb.com/archives/webstock_2009.php</link>
         <guid>http://www.readwriteweb.com/archives/webstock_2009.php</guid>
         <category>Conferences</category>
         <pubDate>Mon, 16 Feb 2009 21:06:13 -0800</pubDate>
<author>Richard MacManus</author>
      </item>
      
   </channel>
</rss>
