<?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: Open Web 0.4: Composability, Interop, Ubiquity, and the Client</title>
	<atom:link href="http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/comment-page-1#comment-266363</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Sun, 03 Aug 2008 23:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3993#comment-266363</guid>
		<description>Sure. It&#039;s general enough it can mean almost anything.</description>
		<content:encoded><![CDATA[<p>Sure. It&#8217;s general enough it can mean almost anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: polterguy</title>
		<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/comment-page-1#comment-266360</link>
		<dc:creator>polterguy</dc:creator>
		<pubDate>Sun, 03 Aug 2008 11:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3993#comment-266360</guid>
		<description>Great list, of course way too general for average Joe to be able to understand what it actually says, but for a list like this to exist more than 5 years I think it should be extremely general. The bright ones among us can always explain what it means to the rest I assume ;)</description>
		<content:encoded><![CDATA[<p>Great list, of course way too general for average Joe to be able to understand what it actually says, but for a list like this to exist more than 5 years I think it should be extremely general. The bright ones among us can always explain what it means to the rest I assume ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/comment-page-1#comment-266347</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Fri, 01 Aug 2008 22:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3993#comment-266347</guid>
		<description>&gt;&gt;Hurray censorship!
.
Wut?</description>
		<content:encoded><![CDATA[<p>&gt;&gt;Hurray censorship!<br />
.<br />
Wut?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: restlessdesign</title>
		<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/comment-page-1#comment-266345</link>
		<dc:creator>restlessdesign</dc:creator>
		<pubDate>Fri, 01 Aug 2008 21:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3993#comment-266345</guid>
		<description>Hurray censorship!</description>
		<content:encoded><![CDATA[<p>Hurray censorship!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/comment-page-1#comment-266332</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Fri, 01 Aug 2008 16:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3993#comment-266332</guid>
		<description>That&#039;s all pretty abstract, and I think the abstractions are just a best-fit around the issues web developers argue about.
.
To me, the actual arguments are much more interesting than any abstractions that fall out.
.
Issues like:
.
1) If JavaScript was allowed by browsers to be supplied in a tokenized state (minus the source), is the Open Web effectively gone?
.
2) Are Flash and Silverlight keeping browsers from going where they should go (example: native Canvas support for IE)?
.
3) Is machine-generated code (from compilers for Java, Ruy, HAXE, etc.) a danger to the Open web because the code is inscrutable?</description>
		<content:encoded><![CDATA[<p>That&#8217;s all pretty abstract, and I think the abstractions are just a best-fit around the issues web developers argue about.<br />
.<br />
To me, the actual arguments are much more interesting than any abstractions that fall out.<br />
.<br />
Issues like:<br />
.<br />
1) If JavaScript was allowed by browsers to be supplied in a tokenized state (minus the source), is the Open Web effectively gone?<br />
.<br />
2) Are Flash and Silverlight keeping browsers from going where they should go (example: native Canvas support for IE)?<br />
.<br />
3) Is machine-generated code (from compilers for Java, Ruy, HAXE, etc.) a danger to the Open web because the code is inscrutable?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SiteSmart</title>
		<link>http://ajaxian.com/archives/open-web-04-composability-interop-ubiquity-and-the-client/comment-page-1#comment-266331</link>
		<dc:creator>SiteSmart</dc:creator>
		<pubDate>Fri, 01 Aug 2008 15:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3993#comment-266331</guid>
		<description>It&#039;s interesting that developer&#039;s are working hard to make the web more open while governments and corporations aew working just as hard to close it up. Then there is browser support...sigh...will we ever really have the Open Web?</description>
		<content:encoded><![CDATA[<p>It&#8217;s interesting that developer&#8217;s are working hard to make the web more open while governments and corporations aew working just as hard to close it up. Then there is browser support&#8230;sigh&#8230;will we ever really have the Open Web?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

