<?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>Winn.ws &#187; Google</title>
	<atom:link href="http://winn.ws/archives/tag/google/feed" rel="self" type="application/rss+xml" />
	<link>http://winn.ws</link>
	<description>Standards-based design &#38; development</description>
	<lastBuildDate>Thu, 09 Sep 2010 14:05:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Wave goodbye</title>
		<link>http://winn.ws/archives/473</link>
		<comments>http://winn.ws/archives/473#comments</comments>
		<pubDate>Wed, 04 Aug 2010 21:34:34 +0000</pubDate>
		<dc:creator>Greg Winn</dc:creator>
				<category><![CDATA[Design & Layout]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[The Web]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Wave]]></category>

		<guid isPermaLink="false">http://winn.ws/?p=473</guid>
		<description><![CDATA[From the official <a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html">Google blog</a>. They announced today that they will no longer be supporting Google Wave by the end of the year.]]></description>
			<content:encoded><![CDATA[<p>From the official <a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html">Google blog</a>. They announced today that they will no longer be supporting Google Wave by the end of the year.</p>
<blockquote><p>But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects. The central parts of the code, as well as the protocols that have driven many of Wave’s innovations, like drag-and-drop and character-by-character live typing, are already available as open source, so customers and partners can continue the innovation we began. In addition, we will work on tools so that users can easily “liberate” their content from Wave.</p></blockquote>
<p><small><a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html">From the official Google blog.</a></small></p>
<p>I for one am a huge Google Wave fan and hate to see this go. Why Google? Why!?</p>
]]></content:encoded>
			<wfw:commentRss>http://winn.ws/archives/473/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Welcome to the future</title>
		<link>http://winn.ws/archives/250</link>
		<comments>http://winn.ws/archives/250#comments</comments>
		<pubDate>Wed, 23 Sep 2009 20:35:37 +0000</pubDate>
		<dc:creator>Greg Winn</dc:creator>
				<category><![CDATA[Design & Layout]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[web standards]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[IE]]></category>

		<guid isPermaLink="false">http://www.winn.ws/?p=250</guid>
		<description><![CDATA[A thorn in the side of many web developers is Internet Explorer 6. It&#8217;s an old browser that has many annoyances that cause those creating websites to have to add additional code just to have things render as they should. Google, being a company that develops a web browser, has taken it upon themselves to [...]]]></description>
			<content:encoded><![CDATA[<p>A thorn in the side of many web developers is Internet Explorer 6. It&#8217;s an old browser that has many annoyances that cause those creating websites to have to add additional code just to have things render as they should. Google, being a company that develops a web browser, has taken it upon themselves to solve this problem somewhat. It has just released an early version of a project called Google Chrome Frame, which, when used, will cause Internet Explorers 6 through 8 to use Chrome&#8217;s rendering engine, not their default one. This allows stubborn users (or those in a workplace environment) to continue using the browser they want to, and no longer aggravate web developers.</p>
<p><a href="http://blog.chromium.org/2009/09/introducing-google-chrome-frame.html">Read more about Google&#8217;s Chrome Frame</a></p>
<p>Thanks Google!</p>
]]></content:encoded>
			<wfw:commentRss>http://winn.ws/archives/250/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mail Goggles from Google!</title>
		<link>http://winn.ws/archives/168</link>
		<comments>http://winn.ws/archives/168#comments</comments>
		<pubDate>Tue, 07 Oct 2008 15:16:07 +0000</pubDate>
		<dc:creator>Greg Winn</dc:creator>
				<category><![CDATA[Platforms]]></category>
		<category><![CDATA[web standards]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.winn.ws/?p=168</guid>
		<description><![CDATA[No More drunk emails!

When you enable Mail Goggles, it will check that you&#8217;re really sure you want to send that late night Friday email. And what better way to check than by making you solve a few simple math problems after you click send to verify you&#8217;re in the right state of mind?

Google Blog
]]></description>
			<content:encoded><![CDATA[<p>No More drunk emails!</p>
<blockquote><p>
When you enable Mail Goggles, it will check that you&#8217;re really sure you want to send that late night Friday email. And what better way to check than by making you solve a few simple math problems after you click send to verify you&#8217;re in the right state of mind?
</p></blockquote>
<p><strong><a href="http://gmailblog.blogspot.com/2008/10/new-in-labs-stop-sending-mail-you-later.html">Google Blog</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://winn.ws/archives/168/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>View some Stats</title>
		<link>http://winn.ws/archives/147</link>
		<comments>http://winn.ws/archives/147#comments</comments>
		<pubDate>Fri, 16 May 2008 16:29:55 +0000</pubDate>
		<dc:creator>Greg Winn</dc:creator>
				<category><![CDATA[PHP GuestBook]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.winn.ws/?p=147</guid>
		<description><![CDATA[The latest build of my guestbook v2.4.2 includes built in stats! This will show you the latest activity that has been taking place on your guestbook!

Download the latest via SVN or visit the project page: Winn Guestbook Project
]]></description>
			<content:encoded><![CDATA[<p>The latest build of my guestbook v2.4.2 includes built in stats! This will show you the latest activity that has been taking place on your guestbook!</p>
<p><a href="http://winn.ws/images/guestbook/gb_2-4-2_screen_stats.jpg" rel="lightbox"><img src="http://www.winn.ws/images/guestbook/gb_2-4-2_screen_stats_small.jpg" alt="Stats" /></a></p>
<p>Download the latest via SVN or visit the project page: <a href="http://code.google.com/p/winn-guestbook/">Winn Guestbook Project</a></p>
]]></content:encoded>
			<wfw:commentRss>http://winn.ws/archives/147/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Does Google Do with Its Old Servers?</title>
		<link>http://winn.ws/archives/142</link>
		<comments>http://winn.ws/archives/142#comments</comments>
		<pubDate>Thu, 17 Apr 2008 15:03:46 +0000</pubDate>
		<dc:creator>Greg Winn</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Servers]]></category>

		<guid isPermaLink="false">http://www.winn.ws/?p=142</guid>
		<description><![CDATA[Google is the fastest growing tech company in the world. Their blazing fast search engine and other services run on thousands of servers. But like all servers, Google&#8217;s servers get old and must be replaced. Google obviously just can&#8217;t give these servers to any old Joe. After all, Google is known for its secrecy and [...]]]></description>
			<content:encoded><![CDATA[<p>Google is the fastest growing tech company in the world. Their blazing fast search engine and other services run on thousands of servers. But like all servers, Google&#8217;s servers get old and must be replaced. Google obviously just can&#8217;t give these servers to any old Joe. After all, Google is known for its secrecy and protectiveness. Most importantly, they don&#8217;t want any data from their servers ending up in the wrong hands. Many of Google&#8217;s servers must contain personal information about employees, Adwords and Adsense members, and probably code for their various services. What exactly does Google do with these servers?</p>
<p><strong>1. Put Them to Use</strong><br />
Just because a server is old doesn&#8217;t mean it isn&#8217;t useful. A server that was too old to be used on their main infrastructure could be used for various other tasks, such as testing projects under development or running various applications needed for the use of employees and internal resources. I think this is a very plausible situation because servers are so expensive and costly to move. Not all applications require powerful servers and I wouldn&#8217;t be surprised to hear that by the time Google was done with a server, it was still fairly new.</p>
<p><strong>2. Grave Scenario</strong><br />
Considering there is a Google search engine for almost every country in the world and in every time zone, someone is always searching on Google. My guess is their servers never, ever get a break. With the amount of servers Google needs, they must have their servers setup so that each one is always working at full capacity and server power is never wasted. For example, if a server wasn&#8217;t handling massive United States search traffic during the day, it could be processing data for search engine rankings, updating databases, or maybe even handling searches from people in other countries at night. </p>
<p>With this kind of abuse, I wouldn&#8217;t be surprised if someone told me Google&#8217;s servers had a short life span. In most environments, servers almost always get a break. For instance, a server in a corporate environment would be busy all day but after everyone left for the day, quiet all night. Without this kind of break, a server&#8217;s life span is more than likely decreased greatly. </p>
<p>3. Give Back to the Tech World<br />
Who is to say Google is mean and greedy with its processing power? From this blog written in 2004 we can find out that Google is donating some of its old servers to Wikipedia. This page at Wikimedia, however, suggests the opposite, when it talks about Google hosting Wikimedia and says:</p>
<blockquote><p><em>&#8220;Google is eager to help us, and Wikimedia are eager to accept their help, but the Board wants to be good stewards of donor money, and this requires them to move carefully.&#8221;</em></p>
</blockquote>
<p>Clearly, this means there is money involved here, not free servers! So, who really knows what Google does with their old servers? Maybe it&#8217;s just one of life&#8217;s little secrets we&#8217;ll never know&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://winn.ws/archives/142/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching 4/10 queries in 0.003 seconds using memcached
Content Delivery Network via Amazon Web Services: CloudFront: dhbbuddo7esu2.cloudfront.net

Served from: winn.ws @ 2010-09-09 22:30:41 -->