<?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: XHTML: Technology Against Users</title>
	<atom:link href="http://ifacethoughts.net/2007/03/12/xhtml-technology-against-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://ifacethoughts.net/2007/03/12/xhtml-technology-against-users/</link>
	<description>Thoughts on software development and related, by Abhijit Nadgouda</description>
	<lastBuildDate>Sun, 21 Mar 2010 09:59:15 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Is Forgiveness The Best Approach? on iface thoughts</title>
		<link>http://ifacethoughts.net/2007/03/12/xhtml-technology-against-users/comment-page-1/#comment-46837</link>
		<dc:creator>Is Forgiveness The Best Approach? on iface thoughts</dc:creator>
		<pubDate>Sun, 29 Apr 2007 16:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2007/03/12/xhtml-technology-against-users/#comment-46837</guid>
		<description>[...] Frankly, at the first instance, I do not like it. Forgiveness implies ignoring the errors, the errors that come out of not doing something right. And that not something right will keep haunting, will keep hindering further development. The part that I do agree with is to not let the error be all over the application. There should be a way to handle the error gracefully, and give better options to the user rather than show the error directly. The draconian handling with XHTML is one of the reasons I think it has been posed against the users&#8217; interest. [...]</description>
		<content:encoded><![CDATA[<p>[...] Frankly, at the first instance, I do not like it. Forgiveness implies ignoring the errors, the errors that come out of not doing something right. And that not something right will keep haunting, will keep hindering further development. The part that I do agree with is to not let the error be all over the application. There should be a way to handle the error gracefully, and give better options to the user rather than show the error directly. The draconian handling with XHTML is one of the reasons I think it has been posed against the users&#8217; interest. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://ifacethoughts.net/2007/03/12/xhtml-technology-against-users/comment-page-1/#comment-17092</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Mon, 12 Mar 2007 00:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2007/03/12/xhtml-technology-against-users/#comment-17092</guid>
		<description>Good point. To the average end user, the technology is so transparent, that one wouldn&#039;t notice the difference between broken HTML and valid XHTML. Browsers are build for handling faults.</description>
		<content:encoded><![CDATA[<p>Good point. To the average end user, the technology is so transparent, that one wouldn&#8217;t notice the difference between broken HTML and valid XHTML. Browsers are build for handling faults.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
