<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: When Utility Isn&#8217;t Enough</title>
	<atom:link href="http://infrequently.org/2007/02/when-utility-isnt-enough/feed/" rel="self" type="application/rss+xml" />
	<link>http://infrequently.org/2007/02/when-utility-isnt-enough/</link>
	<description></description>
	<lastBuildDate>Thu, 10 May 2012 17:22:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Travis Ennis &#187; Blog Archive &#187; Where Goes the Web?</title>
		<link>http://infrequently.org/2007/02/when-utility-isnt-enough/comment-page-1/#comment-98465</link>
		<dc:creator>Travis Ennis &#187; Blog Archive &#187; Where Goes the Web?</dc:creator>
		<pubDate>Fri, 30 Mar 2007 16:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=599#comment-98465</guid>
		<description>[...] I was hooked. Yet, I never could get past the fact the Flex was built on a proprietary technology. I read a few articles by respected developers in the open-source standards community that helped reinforce my belief that developing in a proprietary format went against the spirit of the web. Two articles really stuck out in my mind. The first was Brendan Eich&#8217;s The Open Web and Its Adversaries and the other was a post by Alex Russell. So, I began to feel that with all of the difficulties with developing using standards like XHTML, CSS, and Javascript, those standards were the healthy, open building blocks upon which the web should be built. [...]</description>
		<content:encoded><![CDATA[<p>[...] I was hooked. Yet, I never could get past the fact the Flex was built on a proprietary technology. I read a few articles by respected developers in the open-source standards community that helped reinforce my belief that developing in a proprietary format went against the spirit of the web. Two articles really stuck out in my mind. The first was Brendan Eich&#8217;s The Open Web and Its Adversaries and the other was a post by Alex Russell. So, I began to feel that with all of the difficulties with developing using standards like XHTML, CSS, and Javascript, those standards were the healthy, open building blocks upon which the web should be built. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rounding Off the Edges - Nate Koechley&#8217;s Blog</title>
		<link>http://infrequently.org/2007/02/when-utility-isnt-enough/comment-page-1/#comment-77524</link>
		<dc:creator>Rounding Off the Edges - Nate Koechley&#8217;s Blog</dc:creator>
		<pubDate>Mon, 05 Feb 2007 06:46:57 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=599#comment-77524</guid>
		<description>[...] In Alex Russell&#8217;s latest blog post, When Utility Isn’t Enough, he writes that he&#8217;s &#8220;starting to focus more and more on the &#8217;sharp edges&#8217; of the web development experience.&#8221; I think he&#8217;s suggesting that we &#8212; tool developers and envelope pushers &#8212; might best spend our time reducing the pain points instead of always chasing the latest advancement. I agree. He continues that: &#8220;rounding off the sharp edges is an exercise in usability: things are only useable (sic) when they do what you expect them to. A system that hurts you more than you expect isn&#8217;t useable. [...]</description>
		<content:encoded><![CDATA[<p>[...] In Alex Russell&#8217;s latest blog post, When Utility Isn’t Enough, he writes that he&#8217;s &#8220;starting to focus more and more on the &#8217;sharp edges&#8217; of the web development experience.&#8221; I think he&#8217;s suggesting that we &#8212; tool developers and envelope pushers &#8212; might best spend our time reducing the pain points instead of always chasing the latest advancement. I agree. He continues that: &#8220;rounding off the sharp edges is an exercise in usability: things are only useable (sic) when they do what you expect them to. A system that hurts you more than you expect isn&#8217;t useable. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ritesh</title>
		<link>http://infrequently.org/2007/02/when-utility-isnt-enough/comment-page-1/#comment-77523</link>
		<dc:creator>Ritesh</dc:creator>
		<pubDate>Mon, 05 Feb 2007 06:38:23 +0000</pubDate>
		<guid isPermaLink="false">http://alex.dojotoolkit.org/?p=599#comment-77523</guid>
		<description>I totally agree with your point regarding old apps ++. The compiler folk are trying to experiment with new frameworks which let them stay in the compiler world , yet let them code asynchronously. the problem is that it suffers in speed, space( bloat) and outdated programming. The mis conception of open = insecure also doesnt help. There is a drastic change required in the paradigm of web applications, read similar thoughts by me http://rnayak.wordpress.com/2006/11/09/web-application-paradigms/ . its a pity people are non receptive of change.</description>
		<content:encoded><![CDATA[<p>I totally agree with your point regarding old apps ++. The compiler folk are trying to experiment with new frameworks which let them stay in the compiler world , yet let them code asynchronously. the problem is that it suffers in speed, space( bloat) and outdated programming. The mis conception of open = insecure also doesnt help. There is a drastic change required in the paradigm of web applications, read similar thoughts by me <a href="http://rnayak.wordpress.com/2006/11/09/web-application-paradigms/" rel="nofollow">http://rnayak.wordpress.com/2006/11/09/web-application-paradigms/</a> . its a pity people are non receptive of change.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

