<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The &#8220;invention&#8221; of RSS and the snowball effect</title>
	<atom:link href="http://www.wordyard.com/2007/01/02/rss-adoption/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wordyard.com/2007/01/02/rss-adoption/</link>
	<description>Technology, politics, culture</description>
	<pubDate>Mon, 01 Dec 2008 22:42:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Cleo Saulnier</title>
		<link>http://www.wordyard.com/2007/01/02/rss-adoption/#comment-400</link>
		<dc:creator>Cleo Saulnier</dc:creator>
		<pubDate>Wed, 03 Jan 2007 01:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.wordyard.com/?p=1190#comment-400</guid>
		<description>RSS achieved success not because it's good, but because there was nothing else around that was any better.  If something else comes out that works better, RSS will be gone tomorrow.  Bloggers needed ways to inform users of new articles.  RSS was not the only attempt, and RSS itself is still not well integrated into tools.  Many RSS tools are still separate apps.

As an invention, I would not want to be associated with it.  It's a clunky concept based on polling.  Nothing new here.  Just like the rest of the Web, it's yet another badly strung together idea that doesn't work well with anything else.  RSS is rather forced as a concept.  Just like CSS, XML, client-side scripting languages (ever try using something other than JS?) and all the rest, the web is the new DOS.  Only thing is that at least with DOS, you didn't have to worry that the architecture changed at any given time.  With the web, you're constantly writing hacks to make it seem like everything is in order.  That's no way to do things.

I'm an optimist.  And maybe a dreamer.  But we need a web where the client's browser functionality is not limited.  As much as we look at the web as something that provides content, so is the opposite true.  Humans provide servers with content.  So I believe that the browser should have a well-defined API so that web content can be displayed properly using whatever tools they want.  Unfortunately, there's this other bad idea going around that portability is achieved with VM's (completely false BTW).  And so we're stuck with things like RSS, XML and a backwards look at how software should be.

With the New Year, it could signify starting fresh and doing things right.  Who knows?  Maybe someone will come out with something that's actually fun to work with.</description>
		<content:encoded><![CDATA[<p>RSS achieved success not because it&#8217;s good, but because there was nothing else around that was any better.  If something else comes out that works better, RSS will be gone tomorrow.  Bloggers needed ways to inform users of new articles.  RSS was not the only attempt, and RSS itself is still not well integrated into tools.  Many RSS tools are still separate apps.</p>
<p>As an invention, I would not want to be associated with it.  It&#8217;s a clunky concept based on polling.  Nothing new here.  Just like the rest of the Web, it&#8217;s yet another badly strung together idea that doesn&#8217;t work well with anything else.  RSS is rather forced as a concept.  Just like CSS, XML, client-side scripting languages (ever try using something other than JS?) and all the rest, the web is the new DOS.  Only thing is that at least with DOS, you didn&#8217;t have to worry that the architecture changed at any given time.  With the web, you&#8217;re constantly writing hacks to make it seem like everything is in order.  That&#8217;s no way to do things.</p>
<p>I&#8217;m an optimist.  And maybe a dreamer.  But we need a web where the client&#8217;s browser functionality is not limited.  As much as we look at the web as something that provides content, so is the opposite true.  Humans provide servers with content.  So I believe that the browser should have a well-defined API so that web content can be displayed properly using whatever tools they want.  Unfortunately, there&#8217;s this other bad idea going around that portability is achieved with VM&#8217;s (completely false BTW).  And so we&#8217;re stuck with things like RSS, XML and a backwards look at how software should be.</p>
<p>With the New Year, it could signify starting fresh and doing things right.  Who knows?  Maybe someone will come out with something that&#8217;s actually fun to work with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad Dickerson</title>
		<link>http://www.wordyard.com/2007/01/02/rss-adoption/#comment-399</link>
		<dc:creator>Chad Dickerson</dc:creator>
		<pubDate>Wed, 03 Jan 2007 00:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.wordyard.com/?p=1190#comment-399</guid>
		<description>Scott, your account of Salon's use of RSS is right on the money as I recall.  I believe we rolled it out in 1999.  It wasn't until much later that I even became acquainted with the various RSS debates -- we were just doing what was convenient to us at the time.</description>
		<content:encoded><![CDATA[<p>Scott, your account of Salon&#8217;s use of RSS is right on the money as I recall.  I believe we rolled it out in 1999.  It wasn&#8217;t until much later that I even became acquainted with the various RSS debates &#8212; we were just doing what was convenient to us at the time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
