<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Interesting Things &#187; Google</title>
	<atom:link href="http://www.bradshawenterprises.com/blog/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bradshawenterprises.com/blog</link>
	<description>Richard Bradshaw&#039;s idea of what is interesting</description>
	<lastBuildDate>Sat, 10 Dec 2011 17:00:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Video of ChromeOS Early Build</title>
		<link>http://www.bradshawenterprises.com/blog/2009/221/</link>
		<comments>http://www.bradshawenterprises.com/blog/2009/221/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 14:51:09 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[random]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[chromeos]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/2009/221/</guid>
		<description><![CDATA[Just a quick video made of the ChromeOS build found on the chromium.org server. It&#8217;s run on Ubuntu in a virtual machine running on Snow Leopard. Used Quicktime X to record it, which turned out pretty well I think! Not much in there yet, but good to see that parts of it are on the [...]]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2009/221/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>5 terrible SEO ideas</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-terrible-seo-ideas/</link>
		<comments>http://www.bradshawenterprises.com/blog/2008/5-terrible-seo-ideas/#comments</comments>
		<pubDate>Fri, 10 Oct 2008 20:43:44 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Meta element]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=149</guid>
		<description><![CDATA[This post has been updated and moved to 5 terrible SEO tips. Related PostsOctober 15, 2009 -- Video of ChromeOS Early BuildSeptember 6, 2008 -- 3 Ways Google Applications can enhance teachingSeptember 5, 2008 -- Benchmarking Chrome&#8217;s V8 Javascript engineSeptember 2, 2008 -- Google Chrome Memory UsageJune 6, 2008 -- Google Mail Labs now avaliable!]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2008/5-terrible-seo-ideas/feed/</wfw:commentRss>
		<slash:comments>53</slash:comments>
		</item>
		<item>
		<title>3 Ways Google Applications can enhance teaching</title>
		<link>http://www.bradshawenterprises.com/blog/2008/3-ways-google-applications-can-enhance-teaching/</link>
		<comments>http://www.bradshawenterprises.com/blog/2008/3-ways-google-applications-can-enhance-teaching/#comments</comments>
		<pubDate>Sat, 06 Sep 2008 10:17:56 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=133</guid>
		<description><![CDATA[Having recently started working at a school where email, calendars, documents etc are hosted by Google Applications, I felt that it would be worth while incorporating these into my teaching and planning. This post describes the benefits I have found from this in the first few weeks, and will outline some plans that I have [...]]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2008/3-ways-google-applications-can-enhance-teaching/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Benchmarking Chrome&#8217;s V8 Javascript engine</title>
		<link>http://www.bradshawenterprises.com/blog/2008/benchmarking-chromes-v8-javascript-engine/</link>
		<comments>http://www.bradshawenterprises.com/blog/2008/benchmarking-chromes-v8-javascript-engine/#comments</comments>
		<pubDate>Fri, 05 Sep 2008 18:28:24 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Benchmark]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Just-in-time compilation]]></category>
		<category><![CDATA[programming]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=116</guid>
		<description><![CDATA[Having previously looked at the memory usage of Google&#8217;s Chrome, it&#8217;s time to analyse it&#8217;s much mentioned javascript engine, V8. Assumedly named after the engine with the same name, V8 compiles javascript to machine code, rather than bytecode to achieve greater performance. In this respect, it&#8217;s similar to Firefox 3.1&#8242;s TraceMonkey, a JIT javascript compiler again [...]]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2008/benchmarking-chromes-v8-javascript-engine/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Google Chrome Memory Usage</title>
		<link>http://www.bradshawenterprises.com/blog/2008/google-chrome-memory-usage/</link>
		<comments>http://www.bradshawenterprises.com/blog/2008/google-chrome-memory-usage/#comments</comments>
		<pubDate>Tue, 02 Sep 2008 19:23:15 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[software]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Chrome]]></category>
		<category><![CDATA[Internet Explorer 8]]></category>
		<category><![CDATA[Mozilla Firefox]]></category>
		<category><![CDATA[Safari]]></category>
		<category><![CDATA[Web browser]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/2008/09/02/google-chrome-memory-usage/</guid>
		<description><![CDATA[Google Chrome Memory Usage, originally uploaded by Rich Bradshaw. Browsing to about:memory in Google Chrome gives you this interesting display showing memory usage for both itself as well as other browsers running. According to the browser, this is the memory usage of the following browsers on blank pages. (Although Chrome is on the about:memory page, that&#8217;s [...]]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2008/google-chrome-memory-usage/feed/</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
		<item>
		<title>Google Mail Labs now avaliable!</title>
		<link>http://www.bradshawenterprises.com/blog/2008/google-mail-labs-now-avaliable/</link>
		<comments>http://www.bradshawenterprises.com/blog/2008/google-mail-labs-now-avaliable/#comments</comments>
		<pubDate>Fri, 06 Jun 2008 15:19:05 +0000</pubDate>
		<dc:creator>Richard Bradshaw</dc:creator>
				<category><![CDATA[websites]]></category>
		<category><![CDATA[Gmail]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=42</guid>
		<description><![CDATA[Image via Wikipedia Google have released a section in the settings tab of Gmail called labs. This was predicted by a few blogs recently, and it seems to have come true today. The new labs section includes: Quick Links: Add links to the sidebar for any bookmarkable page in Gmail. This lets you add custom [...]]]></description>
		<wfw:commentRss>http://www.bradshawenterprises.com/blog/2008/google-mail-labs-now-avaliable/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

