<?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>New Technology &#38; Parenting - Slackers Inc. &#187; Google Chrome</title>
	<atom:link href="http://www.slackersinc.com/tag/google-chrome/feed" rel="self" type="application/rss+xml" />
	<link>http://www.slackersinc.com</link>
	<description>The musings of a not quite gen-x, not quite gen-y technology geek.</description>
	<lastBuildDate>Tue, 05 Jan 2010 20:37:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Google&#8217;s new browser</title>
		<link>http://www.slackersinc.com/25/googles-new-browser</link>
		<comments>http://www.slackersinc.com/25/googles-new-browser#comments</comments>
		<pubDate>Thu, 04 Sep 2008 14:42:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Upcoming]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[early adopter]]></category>
		<category><![CDATA[Google Chrome]]></category>

		<guid isPermaLink="false">http://www.slackersinc.com/?p=25</guid>
		<description><![CDATA[A new browser has come out, and as with most things related to Google the fanfare around the browser is coming from the eager technology junkees and not from the big G itself.  It's only been...]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.slackersinc.com/wp-content/uploads/2008/09/chrome.jpg"><img class="alignleft size-medium wp-image-28" style="border: 0pt none; margin: 3px 5px;" title="chrome" src="http://www.slackersinc.com/wp-content/uploads/2008/09/chrome-300x217.jpg" alt="" width="300" height="217" /></a>A new browser has come out, and as with most things related to Google the fanfare around the browser is coming from the eager technology junkees and not from the big G itself.  It&#8217;s only been out a few days, but the early reports are that the speed is the key benefit, with availability of plugins as the main counterpoint.</p>
<p>Just how fast is it though?  <a title="Cnet does Chrome speed tests" href="http://news.cnet.com/8301-1001_3-10030888-92.html" target="_blank">Cnet reports</a> that when dealing with Javascript it&#8217;s no contest, Chrome (the new Googlebrowser) is an order of magnitude faster than anything else out there including the beloved Firefox and especially the lethargic Internet Explorer.  In other tests, user comments indicate that anywhere from 2 to 5 times the speed is typical.  Sounds great, right?</p>
<p>Two downfalls to Chrome exist currently &#8211; first, no Mac support exists.  As Mac users, we&#8217;re used to waiting for commercial releases to trickle down but I must say that I&#8217;m a bit disappointed given the relationship between Google and Apple.  I understand the business reasons for targeting the highest volume market first, it&#8217;s just more of an emotional sting given that many Mac users see Apple and Google as the &#8216;dream team&#8217; that will change the world, dethroning Microsoft from it&#8217;s tyranny over desktops everywhere (Although I&#8217;ll admit that MS Media Center is higher on the WAF (wife approval factor) than anything else out there right now).</p>
<p>That may be a bit melodramatic, and I&#8217;ll still be able to try Chrome out via Parallels, but testing for speed in an emulated environment is a bit&#8230;pointless.  Still, it&#8217;s interesting to see Google trying new things to bring the web to it&#8217;s next plateau of potential.  Faster browsing means more advertising for Google, but more rich experiences for users and less dependency on local hardware and storage.</p>
<p>The second downfall is a lack of plugins to enhance the browsing experience.  Plugins are a necessary evil &#8211; they fill gaps in the core application and allow each part to focus on what it does well, but at the same time amature coders and those unfamiliar with the methodologies used for the core application can cause instability in the application which of course is blamed on the browser and not the plugins.  For this reason, Google may choose to limit the plugin set, however that wouldn&#8217;t be very &#8216;open&#8217; of them either.</p>
<p>Early reports are that Chrome has taken a 3% market share already (2.6% according to <a title="Chrome use stats" href="http://getclicky.com/chrome" target="_blank">clicky</a>) which is huge, but growth will likely slow dramatically after the early adopters have done their testing.</p>
<p>All-in-all, an interesting day on the internets&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.slackersinc.com/25/googles-new-browser/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

